Lighting device and lighting system

ABSTRACT

A lighting device includes: a communication unit that communicates with a vehicle which drives autonomously; a diagnostic unit that performs, via the communication unit, diagnosis as to whether the vehicle is being hacked; and a light emitter that emits illumination light onto at least one of the vehicle, a road on which the vehicle travels, or a parking space in which the vehicle parks.

CROSS-REFERENCE OF RELATED APPLICATIONS

This application is the U.S. National Phase under 35 U.S.C. § 371 ofInternational Patent Application No. PCT/JP2020/042865, filed on Nov.17, 2020, which in turn claims the benefit of Japanese Application No.2019-209730, filed on Nov. 20, 2019, the entire disclosures of each ofwhich Applications are incorporated by reference herein in theirentirety.

TECHNICAL FIELD

The present disclosure relates to a lighting device and a lightingsystem that have a function of diagnosing a vehicle, or the like.

BACKGROUND ART

A street light that emits illumination light onto a road isconventionally known. As an example of the street light, PatentLiterature (PTL) 1 discloses a street light that notifies a hazardousarea and a safe area when a disaster occurs.

CITATION LIST Patent Literature

-   [PTL 1] Japanese Unexamined Patent Application Publication No.    2015-213041

SUMMARY OF INVENTION Technical Problem

However, as with the street light disclosed in PTL 1, there are caseswhere road safety cannot be sufficiently improved by merely notifying ahazardous area during a disaster. For example, regardless of whether adisaster occurs, when an autonomously driving vehicle is subjected tohacking (unauthorized outside operation) by a third party, there is theproblem of causing damage to the hacked vehicle and to other vehicles.In response to this problem, for example, if it is possible in everydaylife to readily diagnose whether a vehicle or the like, which is amobile body, is being hacked, damage due to hacking of the vehicle, orthe like, can be reduced.

In view of this, the present disclosure has an object to provide alighting device, and the like, capable of diagnosing whether a vehicle,or the like, is being hacked.

Solution to Problem

In order to achieve the aforementioned object, an aspect of the lightingdevice according to the present disclosure includes: a communicationunit that communicates with a vehicle which drives autonomously; adiagnostic unit that performs, via the communication unit, diagnosis asto whether the vehicle is being hacked; and a light emitter that emitsillumination light onto at least one of the vehicle, a road on which thevehicle travels, or a parking space in which the vehicle parks.

In order to solve the aforementioned problem, an aspect of the lightingsystem according to the present disclosure includes: the lighting devicedescribed above; and an information terminal that communicates with thelighting device.

Furthermore, in order to achieve the aforementioned object, an aspect ofthe lighting system according to the present disclosure includes: alighting device including a communication unit that communicates with avehicle which drives autonomously, and a light emitter that emitsillumination light onto at least one of the vehicle, a road on which thevehicle travels, or a parking space in which the vehicle parks; and avehicle diagnostic device that is communicatively connected to thecommunication unit and performs, via the communication unit, diagnosisas to whether the vehicle is being hacked.

Furthermore, in order to achieve the aforementioned object, an aspect ofthe lighting system according to the present disclosure includes: alighting device that emits illumination light onto at least one of avehicle which drives autonomously, a road on which the vehicle travels,or a parking space in which the vehicle parks; and a vehicle diagnosticdevice including a communication unit that communicates with thelighting device and the vehicle, and a diagnostic unit that performs,via the communication unit, diagnosis as to whether the vehicle is beinghacked.

Furthermore, in order to achieve the aforementioned object, an aspect ofthe lighting device according to the present disclosure includes: acommunication unit that communicates with a mobile body which drivesautonomously; a diagnostic unit that performs, via the communicationunit, diagnosis as to whether the mobile body is being hacked; and alight emitter that emits illumination light onto at least one of themobile body, a road along a travel path in which the mobile bodytravels, or a waiting area in which the mobile body waits.

Advantageous Effects of Invention

The lighting device, and the like, according to the present disclosureare capable of diagnosing whether a vehicle, or the like, is beinghacked. Accordingly, damage due to the hacking of the vehicle, etc., canbe reduced.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating an example installation of a lightingdevice according to Embodiment 1.

FIG. 2 is a block diagram illustrating a configuration of the lightingdevice according to Embodiment 1.

FIG. 3 is a diagram illustrating an example of questions asked to avehicle by a diagnostic unit of the lighting device according toEmbodiment 1.

FIG. 4 is a diagram illustrating software resilience checking actionsperformed on a vehicle by the lighting device according to Embodiment 1.

FIG. 5 is a diagram illustrating an example of an operation log of avehicle obtained by a diagnostic unit of the lighting device accordingto Embodiment 1.

FIG. 6 is a diagram illustrating examples of the notification providedby a light emitter of the lighting device according to Embodiment 1.

FIG. 7 is a flowchart illustrating an operation of the lighting deviceaccording to Embodiment 1.

FIG. 8 is a flowchart illustrating an example of an operation of thediagnostic unit of the lighting device according to Embodiment 1.

FIG. 9 is a flowchart illustrating another example of the operation ofthe diagnostic unit of the lighting device according to Embodiment 1.

FIG. 10 is a flowchart illustrating another example of the operation ofthe diagnostic unit of the lighting device according to Embodiment 1.

FIG. 11 is a flowchart illustrating another example of the operation ofthe diagnostic unit of the lighting device according to Embodiment 1.

FIG. 12 is a diagram illustrating a use example of a lighting deviceaccording to Embodiment 2.

FIG. 13 is a block diagram illustrating a configuration of the lightingdevice according to Embodiment 2.

FIG. 14 is a diagram illustrating a lighting state of a light emitter ofthe lighting device according to Embodiment 2.

FIG. 15 is a flowchart illustrating an operation of the lighting deviceaccording to Embodiment 2.

FIG. 16 is a schematic diagram illustrating a lighting system accordingto Embodiment 3.

FIG. 17 is a diagram illustrating a communication connectionrelationship between lighting apparatuses included in the lightingsystem according to Embodiment 3.

FIG. 18 is a flowchart illustrating an example of an operation of thelighting system according to Embodiment 3.

FIG. 19 is a flowchart illustrating another example of the operation ofthe lighting system according to Embodiment 3.

FIG. 20 is a schematic diagram illustrating a lighting system accordingto Variation 1 of Embodiment 3.

FIG. 21 is a diagram illustrating a communication connectionrelationship between electrical apparatuses included in the lightingsystem according to Variation 1 of Embodiment 3.

FIG. 22 is a schematic diagram illustrating a lighting system accordingto Variation 2 of Embodiment 3.

FIG. 23 is a diagram illustrating a communication connectionrelationship between electrical apparatuses, a controller, and a vehiclediagnostic device included in the lighting system according to Variation2 of Embodiment 3.

FIG. 24 is a block diagram illustrating a part of the configuration ofthe lighting system according to Variation 2 of Embodiment 3.

FIG. 25 is a schematic diagram illustrating a lighting system accordingto Embodiment 4.

FIG. 26 is a block diagram illustrating a configuration of the lightingsystem according to Embodiment 4.

FIG. 27 is a schematic diagram illustrating a lighting system accordingto Embodiment 5.

FIG. 28 is a block diagram illustrating a configuration of the lightingsystem according to Embodiment 5.

FIG. 29 is a schematic diagram illustrating a lighting device of thelighting system according to Embodiment 5.

FIG. 30 is a flowchart illustrating an example of an operation of thelighting system according to Embodiment 5.

FIG. 31 is a schematic diagram illustrating a lighting system accordingto Embodiment 6.

FIG. 32 is a block diagram illustrating a configuration of the lightingsystem according to Embodiment 6.

FIG. 33 is a diagram illustrating an example of operations of thelighting system according to Embodiment 6.

FIG. 34 is a diagram illustrating an example installation of a lightingdevice according to Embodiment 7.

FIG. 35 is a block diagram illustrating a configuration of the lightingdevice according to Embodiment 7.

FIG. 36 is a schematic diagram illustrating a lighting system accordingto Embodiment 8.

FIG. 37 is a block diagram illustrating a configuration of the lightingsystem according to Embodiment 8.

DESCRIPTION OF EMBODIMENTS

A lighting system according to the subsequent embodiments has adiagnostic function of diagnosing whether a vehicle, or the like, thatdrives autonomously is being hacked by a third party. Because thelighting system has the aforementioned diagnostic function, it ispossible to prevent damage due to hacking of a vehicle or the like. Itshould be noted that, in the subsequent embodiments, hacking refers to astranger performing unauthorized access of a computer to causeunintended operation or preventing normal operation of the computer.

Hereinafter, embodiments will be described in detail with reference tothe Drawings. Note that each of the following embodiments shows aspecific example of the present disclosure. The numerical values,shapes, materials, structural components, the arrangement and connectionof the structural components, steps, the processing order of the steps,etc., shown in the following embodiments are mere examples, and thus arenot intended to limit the present disclosure. Furthermore, among thestructural components described in the following embodiments, structuralcomponents not recited in any one of the independent claims whichindicate embodiments according to aspects of the present disclosure aredescribed as optional structural components. The embodiments of thepresent disclosure are not limited by the current independent claims,and may also be expressed by other independent claims.

It should be noted that the respective figures are not necessarilyprecise illustrations. Furthermore, in the respective figures, the samereference signs are given to structural components that aresubstantially the same, and overlapping description thereof may beomitted or simplified.

Embodiment 1 [1-1. Configuration of Lighting Device]

A configuration of lighting device 10 according to Embodiment 1 will bedescribed with reference to FIG. 1 to FIG. 6 .

FIG. 1 is a diagram illustrating an example installation of lightingdevice 10 according to Embodiment 1.

Lighting device 10 is installed in parking space 91 in which vehicle 50is parked, and emits illumination light onto vehicle 50 and parkingspace 91. Although lighting device 10 is installed on an exterior wallof a house, which is an example of building 60, in FIG. 1 , the presentdisclosure is not limited to this, and lighting device 10 may beinstalled on a roof, a fence, a pillar or the like of the house.

Vehicle 50 is a vehicle capable of autonomous driving, such as anautomobile or a motorcycle. The autonomous driving means that thevehicle drives autonomously and includes not only unmanned driving butalso that the driver is assisted in steering or braking the vehicle.Vehicle 50 may be a vehicle that can switch between a manual drivingmode and an autonomous driving mode. Vehicle 50 is provided withcommunication antenna 51 for communicating with lighting device 10 andcamera 52 that recognizes the illumination light of lighting device 10.Vehicle 50 has an AI assistant function (a software agent). Note thatvehicle 50 is an example of a mobile body, which will be describedlater.

FIG. 2 is a block diagram illustrating a configuration of lightingdevice 10. FIG. 2 also illustrates a computer communicatively connectedto lighting device 10 via a network.

As shown in FIG. 2 , lighting device 10 includes communication unit 11that communicates with vehicle 50, light emitter 12 that can emitillumination light, detector 13 that detects vehicle 50, and diagnosticunit 16 that diagnoses vehicle 50 as to whether an autonomous drivingprogram of vehicle 50 is being hacked. Lighting device 10 furtherincludes controller 15 that controls turning on and off, dimming, andtoning of light emitter 12.

Light emitter 12 is a light source that emits illumination light, and isa liquid crystal projector that projects a static image or moving imageor a light emitting diode (LED) light emitting module that emits lightof red color, green color, or blue color, or synthetic light of thesecolors. Light emitter 12 may be a combination of separate surface mountdevices (SMDs) and chips on board (COBs) of RGB, incandescent bulb color(2700K), neutral white color (5000K), and other colors. Light emitter 12is provided at a position higher than the height of vehicle 50, in orderto illuminate vehicle 50 and surroundings of vehicle 50.

Detector 13 is a sensor that detects the presence or absence of vehicle50 in parking space 91, such as an image sensor, an infrared sensor, ora laser sensor. Detector 13 is constantly operating, and detects whethervehicle 50 is parked in parking space 91. In the present embodiment,light emitter 12 is turned on in response to detector 13 detectingvehicle 50, and diagnostic unit 16 is enabled to diagnose vehicle 50 inresponse to turning on of light emitter 12.

Communication unit 11 is a communication module that communicates withvehicle 50 by radio r1. The communication scheme based on radio r1 maybe Bluetooth®, a specified low power radio using a frequency in the 920MHz band, Zigbee®, or WiFi®, for example.

Controller 15 is formed by a microprocessor, memory 15 a, and a programstored in memory 15 a, for example. Memory 15 a stores identificationinformation on vehicle 50, such as a license plate number. An operationlog and a diagnosis result of vehicle 50 described later are alsorecorded in memory 15 a. Controller 15 controls turning on and the likeof light emitter 12, and controls operations of communication unit 11,detector 13, and diagnostic unit 16.

When detector 13 detects vehicle 50, for example, controller 15transmits, to vehicle 50, a request signal that requests for theidentification information on vehicle 50 via communication unit 11.Controller 15 issues a diagnosis command to diagnostic unit 16 to makediagnostic unit 16 diagnose vehicle 50, when the identificationinformation on vehicle 50 transmitted from vehicle 50 agrees withidentification information registered in advance.

Instead of transmitting the request signal described above, controller15 may establish a communication with vehicle 50, which is triggered byvisible light communication from light emitter 12 to vehicle 50, andobtain the identification information on vehicle 50. In that case,vehicle 50 may decipher information transmitted by the visible lightcommunication by means of camera 52, which is a signal receiver in thevisible light communication, and transmit the identification informationon vehicle 50 to lighting device 10. Controller 15 may obtain theidentification information on vehicle 50 by imaging the license plate bymeans of detector 13. Instead of using detector 13, controller 15 mayobtain the identification information on vehicle 50 by requesting fortransmission of the identification information from vehicle 50 byregularly transmitting a beacon signal from communication unit 11. Thatis, controller 15 may detect vehicle 50 by means of communication unit11 and then perform diagnosis via communication unit 11.

Diagnostic unit 16 is a circuit that diagnoses, via communication unit11, whether vehicle 50 is being hacked. When the lighting state of lightemitter 12 changes, for example, diagnostic unit 16 performs diagnosisof vehicle 50 parked in parking space 91. Specifically, diagnostic unit16 performs diagnosis of the presence of hacking of vehicle 50 whenlight emitter 12 changes from an off state to an on state and diagnosticunit 16 has received a diagnosis command from controller 15.

Diagnostic unit 16 may perform diagnosis of the presence of hacking ofvehicle 50 not only when light emitter 12 changes from the off state tothe on state but also when light emitter 12 changes from the on state tothe off state or a dimmed state or when the lighting color changes.Furthermore, diagnostic unit 16 may end the diagnosis of the presence ofhacking of vehicle 50 when the lighting state changes again after lightemitter 12 changes from the on state to the off state or the dimmedstate or after the lighting color changes. Note that the dimmed state isa state in which a toning control is being performed so that thebrightness of the light is less than or equal to a predeterminedbrightness, for example, a state where the lighting is controlled sothat the illuminance is 30%. That the lighting color changes means astate where a toning control is performed so that the color temperaturechanges.

Here, a vehicle diagnosis by diagnostic unit 16 will be described withregard to three diagnosis examples.

A first diagnosis example is an example in which a vehicle diagnosis isperformed based on an answer to a question asked to vehicle 50 bylighting device 10. Diagnostic unit 16 asks vehicle 50 a plurality ofquestions, and determines whether vehicle 50 is being hacked based on atleast one of the answering time or the answer tendency to the questions.

FIG. 3 is a diagram illustrating an example of questions asked tovehicle 50 by diagnostic unit 16 of lighting device 10.

For example, diagnostic unit 16 asks vehicle 50 a question having auniquely-determined answer via communication unit 11, and diagnoses thatvehicle 50 is being hacked when the answering time to the question isslower than a predetermined time.

A question that is uniquely answered is a question as to the number ofthe occupants of vehicle 50, the destination of vehicle 50, the seatposition of the owner of vehicle 50, the temperature difference betweenthe inside and outside of the vehicle, or the presence of a brakingoperation, for example. The number of the occupants of vehicle 50 can beobtained with camera 52 of vehicle 50. The destination of vehicle 50 canbe obtained with a car navigation system. The temperature differencebetween the inside and outside of the vehicle can be obtained with atemperature sensor. The seat position of the owner can be obtained bythe owner registering the seat position in vehicle 50 in advance. Thepresence of a braking operation can be determined by an electroniccontrol unit (ECU) of vehicle 50.

Since vehicle 50 can instantaneously obtain the number of the occupants,the destination, the seat position, the temperature difference, and thepresence of a braking operation described above, vehicle 50 can answerthe question in a short time if vehicle 50 is normal. Therefore,diagnostic unit 16 determines that vehicle 50 is being hacked when theanswering time to the question is longer than a predetermined time, anddetermines that vehicle 50 is not being hacked when the answering timefalls within the predetermined time. Note that the question that isuniquely answered and the answer to the question may be a question as toa steering operation command or a braking operation command, which areinspection items of the vehicle inspection (VI), and the response tosuch an operation command.

Furthermore, for example, diagnostic unit 16 asks vehicle 50 questionshaving answers that are non-uniquely-determined via communication unit16, and diagnoses that vehicle 50 is being hacked when an amount ofvariation in the answers to the questions is smaller than apredetermined amount of variation. The variation of the answers meansthe degree of variation of answers to similar questions.

The question that is not uniquely answered is a question as to the moodor disposition of the owner, the criterion for determining the travelroute, the level of satisfaction of the owner with vehicle 50, the levelof happiness of the owner, or the weather conditions of the peripheralarea of vehicle 50, for example. The mood or disposition of the ownercan be determined by detecting words and actions of the owner with amicrophone and camera 52 in the vehicle. The criterion for determiningthe travel route can be obtained from a favorite travel route of theowner registered in advance. The level of satisfaction of the owner withvehicle 50 can be determined by detecting how the owner treats orhandles vehicle 50 with a microphone or camera 52. The level ofhappiness of the owner can be determined by detecting the facialexpressions of the owner with camera 52. The weather conditions of theperipheral area of vehicle 50 can be obtained with camera 52 or aweather sensor provided in vehicle 50.

The mood or disposition of the owner, the criterion for determining thetravel route, the level of satisfaction, the level of happiness, and theweather conditions described above vary with the weather, the trafficconditions, the price index, the work progress, interpersonalrelationships or the like, and the answer will vary if vehicle 50 isnormal. However, if vehicle 50 is being hacked by a third party, thevariation of the answers is often small, or the answers are oftensimilar. In view of this, diagnostic unit 16 determines that vehicle 50is not being hacked when the variation of the answers to a plurality ofquestions is greater than or equal to a predetermined variation, anddetermines that vehicle 50 is being hacked when the variation of theanswers is smaller than the predetermined variation.

In this way, lighting device 10 can diagnose whether vehicle 50 is beinghacked through exchange of questions and answers between lighting device10 and vehicle 50.

A second diagnosis example is an example in which a vehicle diagnosis isperformed by checking the resilience of software that runs a travelsystem provided in vehicle 50. Diagnostic unit 16 performs the diagnosisby checking resilience of software which runs a travel system providedin vehicle 50, via communication unit 11. In addition, diagnostic unit16 diagnoses that vehicle 50 is being hacked when a level of theresilience of the software is lower than a predetermined level. Notethat in diagnosis of vehicle 50, checking the vulnerability of softwareis substantially the same as checking the resilience of software.

FIG. 4 is a diagram illustrating software resilience checking actionsperformed on vehicle 50 by lighting device 10.

For example, diagnostic unit 16 checks the resilience of the software byperforming at least one of a denial-of-service (DoS) attack or a bufferoverflow attack on vehicle 50 via communication unit 11. The DoS attackis to transmit a massive number of data packets or request packets tovehicle 50. The buffer overflow attack is to transmit an unallowableamount of data to a microprocessor of vehicle 50 to slow down theprocessing of the microprocessor.

When vehicle 50 is being hacked, such simulated attacks cause changes invehicle 50, such as an extreme slowdown of the processing speed ofsoftware in vehicle 50. Therefore, diagnostic unit 16 performs suchsimulated attacks on vehicle 50, and determines that vehicle 50 is notbeing hacked when the resilience level of vehicle 50 does not decreaseto below a predetermined level, and determines that vehicle 50 is beinghacked when the resilience level decreases to below the predeterminedlevel. As shown in Table 1, the resilience level of software means thelevel of resilience to the simulated attacks and transmission of trapdata described later. The predetermined resilience level is set to level5 or 4, for example.

TABLE 1 Resilience level Determination criterion 5 Resilient to bothsimulated attacks, DoS attack and buffer overflow attack, andtransmission of trap data 4 Resilient to both simulated attacks, DoSattack and buffer overflow attack, and no backdoor is created tosoftware 3 Resilient to both simulated attacks, DoS attack and bufferoverflow attack, but a backdoor is created to software 2 Not resilientto both simulated attacks, DoS attack and buffer overflow attack 1 Notresilient to DoS attack

For example, when the DoS attack causes the level of the resilience ofthe software to become lower than the predetermined level, diagnosticunit 16 may continue the DoS attack until the software of vehicle 50ceases to function, to cause the travel system provided in vehicle 50 toshut down.

Furthermore, diagnostic unit 16 checks the resilience of the software byperforming transmission of trap data to vehicle 50 via communicationunit 11. The transmission of trap data is a measure against a backdoorcreated by a hacker. The trap data contains a trap for checking whetheran important item, such as a log-in ID or vehicle inspectioninformation, has been accessed by a hacker through a backdoor, or a trapfor checking whether a hacker has intruded through a backdoor at thetime of version up of software.

Diagnostic unit 16 transmits trap data to vehicle 50, and determinesthat vehicle 50 is not being hacked when no unauthorized access orunauthorized intrusion has occurred, and determines that vehicle 50 isbeing hacked when the unauthorized access or unauthorized intrusiondescribed above has occurred. For example, when a backdoor to thesoftware is found through the transmission of the trap data, diagnosticunit 16 may diagnose that the level of the resilience of the software islower than the predetermined level and that vehicle 50 is being hacked.

In this way, lighting device 10 can diagnose whether vehicle 50 is beinghacked by checking the resilience of software in vehicle 50.

A third diagnosis example is an example in which an operation log ofvehicle 50 is obtained, and a vehicle diagnosis is performed based onthe operation log. Diagnostic unit 16 obtains an operation log ofvehicle 50 via communication unit 11, and diagnoses that vehicle 50 isbeing hacked, when diagnostic unit 16 confirms that vehicle 50 is notfollowing a predetermined operational regulation.

FIG. 5 is a diagram illustrating an example of an operation log of avehicle obtained by diagnostic unit 16 of lighting device 10.

The operation log includes date and time, location (latitude andlongitude), speed of vehicle 50, and steering wheel angle of vehicle 50,for example. The operational regulation is a regulation about suddenstop, the sudden start, the steering wheel turning angle, or the maximumspeed of vehicle 50, for example. Diagnostic unit 16 determines whethervehicle 50 is driving according to the operational regulation.Diagnostic unit 16 determines that vehicle 50 has been hacked whenvehicle 50 is not following a predetermined operational regulation, anddetermines that vehicle 50 has not been hacked when vehicle 50 isfollowing the operational regulation.

In this way, whether vehicle 50 is being hacked can be diagnosed bydiagnostic unit 16 obtaining an operation log of vehicle 50 andperforming a vehicle diagnosis based on the operation log.

When diagnostic unit 16 has diagnosed that vehicle 50 is being hacked,controller 15 notifies that vehicle 50 is being hacked usingillumination light from light emitter 12. For example, when lightemitter 12 is a liquid crystal projector, controller 15 notifiesinformation regarding hacking by illuminating vehicle 50 or parkingspace 91 with a static image or moving image projected by light emitter12.

FIG. 6 is a diagram illustrating examples of the notification providedby lighting device 10.

Part (a) of FIG. 6 illustrates an example in which light notifying that“vehicle is being hacked” is projected onto the hood of vehicle 50, andPart (b) of FIG. 6 illustrates an example in which light representing aword “WARNING” is projected onto the ground of parking space 91. Thenotification projected by light emitter 12 is not limited to charactersbut may be a mark, such as a figure, a symbol.

In this way, a user of vehicle 50 can visually know whether vehicle 50is being hacked. Therefore, the user can take measures to cope with thehacked vehicle 50, and reduce damage due to the hacking of vehicle 50.

In another example of the notification of the diagnosis result, lightingdevice 10 may notify a computer communicatively connected to lightingdevice 10 via a network of the diagnosis result (see FIG. 2 ). Forexample, lighting device 10 may transmit the diagnosis result to amanagement server that is a computer owned by a dealer of vehicle 50.Lighting device 10 may also notify of the diagnosis result bytransmitting an e-mail to an e-mail address registered by the owner ordealer in advance. This allows the owner or dealer to take measures tocope with the hacked vehicle 50 and reduce damage due to the hacking ofvehicle 50.

[1-2. Operation of Lighting Device]

Next, an operation of lighting device 10 according to Embodiment 1 willbe described with reference to FIG. 7 to FIG. 11 .

FIG. 7 is a flowchart illustrating an operation of lighting device 10.

First, vehicle 50 is parked in parking space 91, and detector 13 oflighting device 10 detects vehicle 50 (Step S11).

In the present embodiment, when detector 13 detects vehicle 50, thelighting state of light emitter 12 changes (Step S12). Specifically,light emitter 12 changes from the off state to the on state.

When the lighting state of light emitter 12 changes, diagnostic unit 16of lighting device 10 performs diagnosis of vehicle 50 (Step S13), anddetermines whether vehicle 50 is being hacked (Step S14). When it isdetermined that vehicle 50 is not being hacked, controller 15 records adiagnosis result that vehicle 50 is not being hacked in memory 15 a(Step S15).

On the other hand, when it is determined that vehicle 50 is beinghacked, controller 15 notifies of an anomaly (Step S16). For example,controller 15 notifies of an anomaly by making light emitter 12 emitillumination light to vehicle 50 or parking space 91. Controller 15 thenrecords a diagnosis result that vehicle 50 is being hacked in memory 15a (Step S17). This is the end of the diagnosis of the presence ofhacking of vehicle 50 by lighting device 10.

Here, three examples of the operation of diagnostic unit 16 performed inStep S13 will be described with reference to FIG. 8 to FIG. 11 .

FIG. 8 is a flowchart illustrating an example of the operation ofdiagnostic unit 16 of lighting device 10. FIG. 8 illustrates an examplein which, among questions asked to vehicle 50, a question that isuniquely answered is asked.

First, diagnostic unit 16 asks vehicle 50 a plurality of questions thatare uniquely answered (Step S131). These questions are randomly asked tovehicle 50 at different timings.

Diagnostic unit 16 then determines whether vehicle 50 has answeredwithin a predetermined time (Step S132). When vehicle 50 has answeredwithin the predetermined time (Yes in S132), diagnostic unit 16determines that vehicle 50 is not being hacked (Step S133).

On the other hand, when vehicle 50 has not answered within thepredetermined time (No in S132), diagnostic unit 16 determines thatvehicle 50 is being hacked (Step S134). In this way, the presence ofhacking of vehicle 50 can be diagnosed by asking a question that isuniquely answered.

FIG. 9 is a flowchart illustrating another example of the operation ofdiagnostic unit 16 of lighting device 10. FIG. 9 illustrates an examplein which, of questions asked to vehicle 50, a question that is notuniquely answered is asked.

First, diagnostic unit 16 asks vehicle 50 a plurality of questions thatare not uniquely answered (Step S131A). These questions are randomlyasked to vehicle 50 at different timings.

Diagnostic unit 16 then determines whether or not the variation of theanswers from vehicle 50 is greater than or equal to a predeterminedvariation (Step S132A). When the variation of the answers is greaterthan or equal to the predetermined variation (Yes in S132A), diagnosticunit 16 determines that vehicle 50 is not being hacked (Step S133A).

On the other hand, when the variation of the answers is smaller than thepredetermined variation (No in S132A), diagnostic unit 16 determinesthat vehicle 50 is being hacked (Step S134A). In this way, the presenceof hacking of vehicle 50 can be diagnosed by asking a question that isnot uniquely answered.

Although questions that are uniquely answered and questions that are notuniquely answered have been separately described above, diagnostic unit16 may diagnose the presence of hacking by asking the vehicle bothquestions that are uniquely answered and questions that are not uniquelyanswered in a random manner at different timings.

FIG. 10 is a flowchart illustrating another example of the operation ofdiagnostic unit 16 of lighting device 10. FIG. 10 illustrates an examplein which the resilience of software that runs a travel system providedin vehicle 50 is checked.

First, diagnostic unit 16 transmits, to vehicle 50, data for checkingthe resilience of software (Step S131B).

Diagnostic unit 16 then determines whether the resilience of thesoftware is lower than a predetermined level (Step S132B). When theresilience of the software is not lower than the predetermined level,diagnostic unit 16 determines that vehicle 50 is not being hacked (StepS133B).

On the other hand, when the resilience of the software is lower than thepredetermined level, diagnostic unit 16 determines that vehicle 50 isbeing hacked (Step S134B). Diagnostic unit 16 then continues a simulatedattack until the software ceases to function (Step S135B), therebytaking the travel system provided in vehicle 50 down. In this way, thepresence of hacking of vehicle 50 can be diagnosed by checking theresilience of software.

FIG. 11 is a flowchart illustrating another example of the operation ofdiagnostic unit 16 of lighting device 10. FIG. 11 illustrates an examplein which the presence of hacking of vehicle 50 is determined based on anoperation log of vehicle 50.

First, diagnostic unit 16 obtains an operation log of vehicle 50 (StepS131C).

Diagnostic unit 16 then determines whether vehicle 50 has followed apredetermined operational regulation (Step S132C). When vehicle 50 hasfollowed the predetermined operational regulation (Yes in S132C),diagnostic unit 16 determines that vehicle 50 is not being hacked (StepS133C).

On the other hand, when vehicle 50 has not followed the operationalregulation (No in S132C), diagnostic unit 16 determines that vehicle 50is being hacked (Step S134C). In this way, the presence of hacking ofvehicle 50 can be determined based on an operation log.

As described above, lighting device 10 can diagnose the presence ofhacking of vehicle 50 through the operations shown in FIG. 8 to FIG. 11. Therefore, damage due to the hacking of vehicle 50 can be reduced.

Embodiment 2 2-1. Configuration of Lighting Device

A configuration of lighting device 10A according to Embodiment 2 will bedescribed with reference to FIG. 12 to FIG. 14 . In Embodiment 2, anexample will be described in which lighting device 10A is a portablelighting device.

FIG. 12 is a diagram illustrating a use example of lighting device 10Aaccording to Embodiment 2. FIG. 13 is a block diagram illustrating aconfiguration of lighting device 10A.

As shown in FIG. 12 , lighting device 10A is a portable flashlight andhas a cylindrical or truncated conical shape. As shown in FIG. 13 ,lighting device 10A includes communication unit 11 that communicateswith vehicle 50, light emitter 12 that can emit illumination light,switch 14, diagnostic unit 16 that diagnoses vehicle 50 as to whether anautonomous driving program of vehicle 50 is being hacked, and outputunit 17. Lighting device 10A further includes controller 15 thatcontrols turning on and off, dimming, and toning of light emitter 12.

Light emitter 12 is a light source that emits illumination light, and isan LED light emitting module that emits light of red color, green color,or blue color, or synthetic light of these colors, for example. Lightemitter 12 may be a combination of separate SMDs and COBs of RGB,incandescent bulb color, neutral white color, and other colors. Lightemitter 12 is provided at an end of lighting device 10A in order toilluminate vehicle 50.

Switch 14 is an input unit for an input operation to turn on and offlighting device 10A. In the present embodiment, when switch 14 is turnedon, light emitter 12 is turned on, and diagnostic unit 16 is enabled todiagnose vehicle 50 in response to the turning on of light emitter 12.When switch 14 is turned off, light emitter 12 is turned off, anddiagnostic unit 16 ends the diagnosis of vehicle 50 in response to theturning off of light emitter 12.

Communication unit 11 is a communication module that communicates withvehicle 50 by radio r1. The communication scheme based on radio r1 hasalready been described above.

Output unit 17 is an output terminal for outputting a diagnosis resultfrom diagnostic unit 16 to the outside, and is a universal serial bus(USB) terminal, for example.

Controller 15 is formed by a microprocessor, memory 15 a, and a programstored in memory 15 a, for example. Memory 15 a stores identificationinformation on vehicle 50, such as a license plate number. An operationlog and a diagnosis result of vehicle 50 described later are alsorecorded in memory 15 a. Controller 15 controls turning on and the likeof light emitter 12, and controls operations of communication unit 11,diagnostic unit 16, and output unit 17.

When controller 15 receives an on operation for switch 14, for example,controller 15 transmits, to vehicle 50, a request signal that requestsfor the identification information on vehicle 50 via communication unit11. Controller 15 issues a diagnosis command to diagnostic unit 16 tomake diagnostic unit 16 diagnose vehicle 50, when the identificationinformation on vehicle 50 transmitted from vehicle 50 agrees withidentification information registered in advance. It should be notedthat, instead of transmitting the request signal described above,controller 15 may establish a communication with vehicle 50, which istriggered by visible light communication from light emitter 12 tovehicle 50, and obtain the identification information on vehicle 50.

Diagnostic unit 16 is a circuit that diagnoses, via communication unit11, whether vehicle 50 is being hacked. When the lighting state of lightemitter 12 changes, for example, diagnostic unit 16 performs diagnosisof vehicle 50 parked in parking space 91. Specifically, diagnostic unit16 performs diagnosis of the presence of hacking of vehicle 50 whenlight emitter 12 changes from an off state to an on state and diagnosticunit 16 has received a diagnosis command from controller 15.

The vehicle diagnosis by diagnostic unit 16 will be described withregard to three diagnosis examples.

A first diagnosis example is an example in which a vehicle diagnosis isperformed based on an answer to a question asked to vehicle 50 bylighting device 10. Diagnostic unit 16 asks vehicle 50 a plurality ofquestions, and determines whether vehicle 50 is being hacked based on atleast one of the answering time or the answer tendency to the questions.

A second diagnosis example is an example in which a vehicle diagnosis isperformed by checking the resilience of software that runs a travelsystem provided in vehicle 50. Diagnostic unit 16 checks the resilienceof the software in vehicle 50 via communication unit 11, and diagnosesthat vehicle 50 is being hacked when the resilience level is lower thana predetermined level.

A third diagnosis example is an example in which an operation log ofvehicle 50 is obtained, and a vehicle diagnosis is performed based onthe operation log. Diagnostic unit 16 obtains an operation log ofvehicle 50 via communication unit 11, and diagnoses that vehicle 50 isbeing hacked, when diagnostic unit 16 confirms that vehicle 50 is notfollowing a predetermined operational regulation.

When diagnostic unit 16 has diagnosed that vehicle 50 is being hacked,controller 15 notifies that vehicle 50 is being hacked usingillumination light from light emitter 12.

FIG. 14 is a diagram illustrating the lighting state of light emitter 12of lighting device 10A.

As shown in FIG. 14 , light emitter 12 is fully turned on when switch 14is turned on and lighting device 10A starts diagnosis, and blinks whilelighting device 10A is communicating with vehicle 50 and performingdiagnosis. Light emitter 12 then emits light of blue color when thediagnosis result is that vehicle 50 is not being hacked, and emits lightof red color when the diagnosis result is that vehicle 50 is beinghacked.

In this way, a user of vehicle 50 can visually know whether vehicle 50is being hacked. Therefore, the user can take measures to cope with thehacked vehicle 50, and reduce damage due to the hacking of vehicle 50.

2-2. Operation of Lighting Device

Next, an operation of lighting device 10A according to Embodiment 2 willbe descried.

FIG. 15 is a flowchart illustrating an operation of lighting device 10A.

First, lighting device 10A receives a turn-on operation of switch 14 bya user (Step S21). In response to this, light emitter 12 is turned on(Step S22).

Diagnostic unit 16 of lighting device 10A then performs diagnosis ofvehicle 50 (Step S23), and determines whether vehicle 50 is being hacked(Step S24). When it is determined that vehicle 50 is not being hacked,controller 15 notifies of a normality through light emitter 12 (StepS25), and records a diagnosis result that vehicle 50 is not being hackedin memory 15 a (Step S26).

On the other hand, when it is determined that vehicle 50 is beinghacked, controller 15 notifies of an anomaly (Step S27), and records adiagnosis result that vehicle 50 is being hacked in memory 15 a (StepS28). When lighting device 10A receives a turn-off operation of switch14, lighting device 10A turns off light emitter 12, and ends thediagnosis of the presence of hacking of vehicle 50.

In this manner, lighting device 10A can diagnose the presence of hackingof vehicle 50 through the operations indicated in steps S21 to S28.Therefore, damage due to the hacking of vehicle 50 can be reduced.

Embodiment 3 3-1. Configuration of Lighting System

A configuration of lighting system 1 according to Embodiment 3 will bedescribed with reference to FIG. 16 and FIG. 17 . In Embodiment 3, anexample will be described in which lighting device having a vehiclediagnostic function forms a part of an Internet-of-things (IoT) system.

FIG. 16 is a schematic diagram illustrating lighting system 1 accordingto Embodiment 3.

As shown in FIG. 16 , lighting system 1 is formed by a plurality oflighting apparatuses. Lighting device 10, which has a vehicle diagnosticfunction among the plurality of lighting apparatuses, is installed on anexterior wall of building 60 in order to emit illumination light ontovehicle 50 in parking space 91. Of the plurality of lightingapparatuses, entrance light 61, living-room light 62, staircase light63, bathroom light 64, and bedroom light 65 are installed in anentrance, a living room, a staircase, a bathroom, and a bedroom ofbuilding 60, respectively. Each of these lighting apparatuses has aradio communication function.

FIG. 17 is a diagram illustrating a communication connectionrelationship between the plurality of lighting apparatuses forminglighting system 1.

As shown in FIG. 17 , lighting device 10, entrance light 61, living-roomlight 62, staircase light 63, bathroom light 64, and bedroom light 65form a mesh network and can communicate with each other. Examples of themesh network referred to herein include a Bluetooth® low energy (BLE) adhoc network.

With lighting system 1 according to the present embodiment, diagnosticunit 16 of lighting device 10 starts or ends diagnosis in response tothe lighting state of another lighting apparatus provided in building60. In the following, an operation of lighting system 1 having theconfiguration described above will be described.

3-2. Operation of Lighting System

An operation of lighting system 1 according to Embodiment 3 will bedescribed with reference to FIG. 18 and FIG. 19 .

FIG. 18 is a flowchart illustrating an example of an operation oflighting system 1.

First, when the owner of vehicle 50 gets home, lighting device 10 andentrance light 61 are turned on in response to the owner's getting home(Step S31). The owner then enters the house, and turns on a light in thehouse (Step S32).

For example, at 24 o'clock (0 o'clock), which is the owner's bedtime,the owner enters the bedroom and turns off bedroom light 65 (Step S33).When going to bed, living-room light 62, staircase light 63, and bedroomlight 65 of the plurality of lighting apparatuses included in lightingsystem 1 are turned off in the listed order, that is, in order ofincreasing proximity to the bedroom, and therefore, lighting system 1can recognize that the owner is going to bed. That is, when lightingapparatuses are turned off in sequence in order of increasing proximityto the bedroom, the owner is going to bed, and vehicle 50 will not beused for a long time. Thus, lighting system 1 uses this time to performa vehicle diagnosis (Step S34).

At 6:00, which is the owner's wake-up time, the owner turns on bedroomlight 65 (Step S35). The turning on of bedroom light 65 notifieslighting system 1 that the owner will use vehicle 50 to go to work inseveral tens of minutes. Thus, lighting system 1 ends the vehiclediagnosis when bedroom light 65 is turned on around the wake-up time(Step S36). When ending the vehicle diagnosis, lighting system 1 recordsthe diagnosis result in memory 15 a of lighting device 10.

With lighting system 1, the presence of hacking of vehicle 50 can bediagnosed by taking advantage of turning on or off of a lightingapparatus or other events in daily life. In this way, damage due to thehacking of vehicle 50 can be reduced.

FIG. 19 is a flowchart illustrating another example of the operation oflighting system 1. Steps S31 to S34 are the same as those in FIG. 18 ,and descriptions thereof will be omitted.

Referring to FIG. 19 , a case will be described where at 2:00 at night,the owner needs to go out for some reason. The owner gets up late atnight, and turns on lighting apparatuses in the house, such as bedroomlight 65 (Step S35A). For example, when the owner goes to work, theowner turns on bedroom light 65, living-room light 62, and entrancelight 61 among the lighting apparatuses in the listed order while theowner goes to parking space 91. Since bedroom light 65, living-roomlight 62, and entrance light 61 are turned on in the listed order,lighting system 1 can recognize that the owner will use vehicle 50 to goout soon. Therefore, when the lighting apparatuses are turned on inorder of increasing proximity to the entrance, lighting system 1 endsthe vehicle diagnosis even though late at night (Step S36A). When endingthe vehicle diagnosis, if the vehicle diagnosis is still in process,lighting system 1 records the partial diagnosis result in memory 15 a.In this way, a load on the system and an adverse effect on the systemdue to the forced termination of the vehicle diagnosis can be prevented.

With lighting system 1, the presence of hacking of vehicle 50 can bediagnosed by taking advantage of turning on or off of a lightingapparatus or other events in daily life. In this way, damage due to thehacking of vehicle 50 can be reduced.

Although an example has been shown above in which a plurality oflighting apparatuses forms an IoT system, the present disclosure is notlimited to this, and a smartphone, a smart speaker, or an alarm clockmay be linked with the IoT system. In that case, lighting system 1 maydetermine the start time and the end time of the vehicle diagnosis basedon a schedule recorded in the smartphone, words or actions detected bythe smart speaker, or the wake-up time set in the alarm clock, forexample.

3-3. Variation 1 of Embodiment 3

Next, a configuration of lighting system 1A according to Variation 1 ofEmbodiment 3 will be described with reference to FIG. 20 and FIG. 21 .In Variation 1 of Embodiment 3, again, an example will be described inwhich lighting device 10 having a vehicle diagnostic function forms apart of an IoT system.

FIG. 20 is a schematic diagram illustrating lighting system 1A accordingto Variation 1 of Embodiment 3.

As shown in FIG. 20 , lighting system 1A is formed by a plurality ofelectrical apparatuses. Lighting device 10, which has a vehiclediagnostic function among the plurality of lighting apparatuses, isinstalled on an exterior wall of building 60 in order to emitillumination light onto vehicle 50 in parking space 91. Of the pluralityof electrical apparatuses, entrance light 61, living-room light 62,staircase light 63, bathroom light 64, and bedroom light 65 areinstalled in an entrance, a living room, a staircase, a bathroom, and abedroom of building 60, respectively. In this variation, in building 60,motion sensor 66 and bedroom switch 67 are installed in the bedroom, andlighting controller 69 is installed in the living room.

FIG. 21 is a diagram illustrating a communication connectionrelationship between the plurality of electrical apparatuses forminglighting system 1A.

As shown in FIG. 21 , entrance light 61, living-room light 62, staircaselight 63, bathroom light 64, bedroom light 65, motion sensor 66, andbedroom switch 67 are each communicatively connected to lightingcontroller 69 via a network. Operations of electrical apparatusesincluding the plurality of lighting apparatuses, motion sensor 66, andbedroom switch 67 are each controlled by lighting controller 69.

For example, when motion sensor 66 in the bedroom detects a person, andbedroom switch 67 is turned off, lighting controller 69 turns offbedroom light 65, and diagnosis of vehicle 50 is started by lightingdevice 10. Lighting system 1A according to the variation performsdiagnosis of vehicle 50 when the operational state of at least one ofthe electrical apparatuses changes. Specifically, diagnostic unit 16 oflighting device 10 starts or ends diagnosis in response to the lightingstate or operational state of another electrical apparatus provided inbuilding 60. In this variation, again, the presence of hacking ofvehicle 50 is being hacked can be diagnosed by taking advantage ofturning on or off of a lighting apparatus or other events in daily life.In this way, damage due to the hacking of vehicle 50 can be reduced.

3-4. Variation 2 of Embodiment 3

Next, a configuration of lighting system 18 according to Variation 2 ofEmbodiment 3 will be described with reference to FIG. 22 and FIG. 23 .In Variation 2 of Embodiment 3, an example will be described in whichvehicle diagnostic device 30B of lighting system performs diagnosis ofvehicle 50 in a state where the communication with the apparatuses otherthan vehicle 50 is disconnected.

FIG. 22 is a schematic diagram illustrating lighting system 18 accordingto Variation 2 of Embodiment 3.

As shown in FIG. 22 , lighting system 18 is formed by a plurality ofelectrical apparatuses, controller 69B, and vehicle diagnostic device30B. Vehicle diagnostic device 30B is installed on an exterior wall ofbuilding 60. Of the plurality of electrical apparatuses, entrance light61, living-room light 62, staircase light 63, bathroom light 64, andbedroom light 65 are installed in an entrance, a living room, astaircase, a bathroom, and a bedroom of building 60, respectively.Motion sensor 66 and bedroom switch 67 are installed in the bedroom,door switch 68 is installed on the door of the entrance, and controller69B is installed in the living room.

FIG. 23 is a diagram illustrating a communication connectionrelationship between the plurality of electrical apparatuses, controller69B, and vehicle diagnostic device 30B forming lighting system 18. FIG.24 is a block diagram illustrating a part of the configuration oflighting system 18.

As shown in FIG. 23 , vehicle diagnostic device 30B, entrance light 61,living-room light 62, staircase light 63, bathroom light 64, bedroomlight 65, motion sensor 66, door switch 68, and bedroom switch 67 areeach communicatively connected to controller 69B.

As shown in FIG. 24 , vehicle diagnostic device 30B includescommunication unit 31 that communicates with vehicle 50, anothercommunication unit 32 that communicates with a plurality of electricalapparatuses via a network, diagnostic unit 36 that diagnoses vehicle 50as to whether an autonomous driving program of vehicle 50 is beinghacked, and controller 35 that controls operations of communication unit31, communication unit 32, and diagnostic unit 36.

Controller 35 of vehicle diagnostic device 30B controls diagnostic unit36 to perform diagnosis of vehicle 50 when the operational state of atleast one of the plurality of electrical apparatuses changes. Forexample, “when the operational state of an electrical apparatus changes”means when the lighting state of a lighting apparatus, which is anelectrical apparatus, changes, when motion sensor 66, which is anelectrical apparatus, detects the owner, when bedroom switch 67, whichis an electrical apparatus, is turned off, or when door switch 68, whichis an electrical apparatus, is turned on.

When diagnostic unit 36 perform the diagnosis described above viacommunication unit 31, vehicle diagnostic device 30B according toVariation 2 limits the communication with the plurality of electricalapparatuses via the network and communication unit 32 to only apredetermined communication, such as identification (ID) authentication,and controls diagnostic unit 36 to perform the diagnosis in this state.After the diagnosis ends, vehicle diagnostic device 30B returns thecommunication with the plurality of electrical apparatuses to theoriginal communication state through communication unit 32. In this way,by limiting the communication with the plurality of electricalapparatuses to only a predetermined communication when performingdiagnosis of hacking of vehicle 50, the hacked vehicle 50 can beprevented from adversely affecting the plurality of electricalapparatuses, for example.

Although an example has been shown above in which, in lighting system 18according to Variation 2, vehicle diagnostic device 30B performsdiagnosis of vehicle 50 while limiting the communication with aplurality of electrical apparatuses to only a predeterminedcommunication, the present disclosure is not limited to this. Forexample, vehicle diagnostic device 30B may limit the communication witha plurality of electrical apparatuses to only a predeterminedcommunication, then download an operation log of vehicle 50 bycommunicating with vehicle 50, and then diagnose vehicle 50 based on theoperation log in the state where the communication with vehicle 50 islimited to only a predetermined communication.

Embodiment 4

A configuration of lighting system 1C according to Embodiment 4 will bedescribed with reference to FIG. 25 and FIG. 26 .

In Embodiment 4, an example will be described in which lighting system1C is formed by lighting device 10C and vehicle diagnostic device 30C.

FIG. 25 is a schematic diagram illustrating lighting system 1C accordingto Embodiment 4.

Lighting device 10C and vehicle diagnostic device 30C of lighting system1C are installed in parking space 91 in which vehicle 50 is parked.Although lighting device 10C is installed on a wall of parking space 91in FIG. 25 , the present disclosure is not limited to this, and lightingdevice 10C may be installed on a ceiling, a pillar or the like ofparking space 91.

FIG. 26 is a block diagram illustrating a configuration of lightingsystem 1C. FIG. 26 also illustrates a computer communicatively connectedto lighting system 1C via a network.

As shown in FIG. 26 , lighting system 1C is formed by lighting device10C and vehicle diagnostic device 30C. Lighting device 10C includeslight emitter 12 that can emit illumination light, detector 13 thatdetects vehicle 50, and controller 15 that controls operations of lightemitter 12 and detector 13. Vehicle diagnostic device 30C includescommunication unit 31 that communicates with vehicle 50, diagnostic unit36 that diagnoses vehicle 50 as to whether an autonomous driving programof vehicle 50 is being hacked, and controller 35 that controlsoperations of communication unit 31 and diagnostic unit 36.

Light emitter 12 of lighting device 10C is a light source that emitsillumination light, and is a liquid crystal projector that projects astatic image or moving image, or an LED light emitting module that emitslight of red color, green color, or blue color, or synthetic light ofthese colors, for example. Light emitter 12 may be a combination ofseparate SMDs and COBs of RGB, incandescent bulb color, neutral whitecolor, and other colors. Light emitter 12 is provided at a positionhigher than the height of vehicle 50, in order to illuminate vehicle 50and surroundings of vehicle 50.

Detector 13 of lighting device 10C is a sensor that detects the presenceor absence of vehicle 50 in parking space 91, such as an image sensor,an infrared sensor, or a laser sensor. Detector 13 is constantlyoperating, and detects whether vehicle 50 is parked in parking space 91.In the present embodiment, light emitter 12 is turned on in response todetector 13 detecting vehicle 50, and vehicle diagnostic device 30C isenabled to diagnose vehicle 50 in response to turning on of lightemitter 12.

Communication unit 31 of vehicle diagnostic device 30C is acommunication module that communicates with vehicle 50 by radio r1. Thecommunication scheme based on radio r1 has already been described above.

Controller 35 of vehicle diagnostic device 30C is formed by amicroprocessor, memory 35 a, and a program stored in memory 35 a, forexample. Memory 35 a stores identification information on vehicle 50,such as a license plate number. An operation log and a diagnosis resultof vehicle 50 described later are also recorded in memory 35 a.

When detector 13 detects vehicle 50, and controller 35 obtains thedetection information from lighting device 10C, for example, controller35 transmits, to vehicle 50, a request signal that requests for theidentification information on vehicle 50 via communication unit 31.Controller 35 issues a diagnosis command to diagnostic unit 36 to makediagnostic unit 36 diagnose vehicle 50, when the identificationinformation on vehicle 50 transmitted from vehicle 50 agrees withidentification information registered in advance.

Instead of transmitting the request signal described above, controller35 may establish a communication with vehicle 50, which is triggered byvisible light communication from light emitter 12 to vehicle 50, andobtain the identification information on vehicle 50. Alternatively,controller 35 may obtain the identification information on vehicle 50 byimaging the license plate by means of detector 13. Instead of usingdetector 13, controller 35 may obtain the identification information onvehicle 50 by requesting for transmission of the identificationinformation from vehicle 50 by regularly transmitting a beacon signalfrom communication unit 31. That is, controller 35 may detect vehicle 50by means of communication unit 31 and then perform diagnosis viacommunication unit 31.

Diagnostic unit 36 is a circuit that diagnoses, via communication unit31, whether vehicle 50 is being hacked. When the lighting state of lightemitter 12 changes, for example, diagnostic unit 36 perform diagnosis ofvehicle 50 parked in parking space 91. Specifically, diagnostic unit 36performs diagnosis of the presence of hacking of vehicle 50 when lightemitter 12 changes from the off state to the on state and diagnosticunit 36 has received a diagnosis command from controller 35.

Diagnostic unit 36 may perform the diagnosis not only when light emitter12 changes from the off state to the on state but also when lightemitter 12 changes from the on state to the off state or the dimmedstate or when the lighting color changes. Furthermore, diagnostic unit36 may end the diagnosis of the presence of hacking of vehicle 50 whenthe lighting state changes again after light emitter 12 changes from theon state to the off state or the dimmed state or after the lightingcolor changes.

There are three examples of the vehicle diagnosis by diagnostic unit 36.

A first diagnosis example is an example in which a vehicle diagnosis isperformed based on an answer to a question asked to vehicle 50 byvehicle diagnostic device 30C. Diagnostic unit 36 asks vehicle 50 aplurality of questions, and determines whether vehicle 50 is beinghacked based on at least one of the answering time or the answertendency to the questions.

A second diagnosis example is an example in which a vehicle diagnosis isperformed by checking the resilience of software that runs a travelsystem provided in vehicle 50. Diagnostic unit 36 checks the resilienceof the software in vehicle 50 via communication unit 31, and diagnosesthat vehicle 50 is being hacked when the resilience level is lower thana predetermined level.

A third diagnosis example is an example in which an operation log ofvehicle 50 is obtained, and a vehicle diagnosis is performed based onthe operation log. Diagnostic unit 36 obtains the operation log ofvehicle 50 via communication unit 31, and diagnoses that vehicle 50 hasbeen hacked when vehicle 50 is not following a predetermined operationalregulation.

When diagnostic unit 36 has diagnosed that vehicle 50 is being hacked,controller 35 notifies that vehicle 50 is being hacked usingillumination light from light emitter 12. For example, when lightemitter 12 is a liquid crystal projector, controller 35 notifiesinformation regarding hacking by illuminating vehicle 50 or parkingspace 91 with a static image or moving image projected by light emitter12.

In this way, the user of vehicle 50 can know whether vehicle 50 is beinghacked. Therefore, the user can take measures to cope with the hackedvehicle 50, and reduce damage due to the hacking of vehicle 50.

In another example of the notification of the diagnosis result, lightingsystem 1C may notify a computer communicatively connected to lightingsystem 1C via a network of the diagnosis result (see FIG. 26 ). Forexample, lighting system 1C may transmit the diagnosis result to amanagement server that is a computer owned by a dealer of vehicle 50.Lighting system 1C may also notify of the diagnosis result bytransmitting an e-mail to an e-mail address registered by the owner ordealer in advance. This allows the owner or dealer to take measures tocope with the hacked vehicle 50 and reduce damage due to the hacking ofvehicle 50.

Embodiment 5 [5-1. Configuration of Lighting System]

A configuration of lighting system 1D according to Embodiment 5 will bedescribed with reference to FIG. 27 to FIG. 29 . In Embodiment 5, anexample will be described in which lighting device 10D diagnoses vehicle50 parked in parking space 91 that is a public parking space.

FIG. 27 is a schematic diagram illustrating lighting system 1D accordingto Embodiment 5.

As shown in FIG. 27 , lighting system 1D includes lighting device 10Dprovided at a side of parking space 91, and information terminal 70 thatcommunicates with lighting device 10D. Information terminal 70 is aportable terminal held by the owner of vehicle 50. Although FIG. 27illustrates one lighting device 10D, lighting system 1D may include aplurality of lighting devices 10D.

Lighting device 10D is a device that emits illumination light to parkingspace 91, and is, for example, an outdoor lighting device such as astreet light, a security light, or the like. Lighting device 10D may beinstalled in a parking space of a park, the premises of an apartmentbuilding, or the premises of a factory, for example.

Lighting device 10D includes pole body 23 installed at a side of parkingspace 91, and lamp 22 provided on pole body 23. Pole body 23 is acolumnar member, and is a utility pole on which a distribution line isprovided, a pole of a street light, or a pole to which a security camerais attached, for example. Pole body 23 may have an L-shape or T-shape.

FIG. 28 is a block diagram illustrating a configuration of lightingsystem 1D. FIG. 29 is a schematic diagram illustrating lighting device10D of lighting system 1D. FIG. 28 also illustrates a computercommunicatively connected to lighting system 1D via a network.

As shown in FIG. 28 , lighting device 10D includes communication unit11, light emitter 12, detector 13, controller 15, and diagnostic unit16.

Communication unit 11 is a communication module that communicates withvehicle 50 by radio r1, and communicates with information terminal 70 byradio r2. The communication scheme based on radio r2 may be Bluetooth®,Zigbee®, or WiFi®, for example. Communication unit 11 may be capable ofcommunicating with information terminal 70 via a network (not shown),such as the Internet. Communication unit 11 transmits a diagnosis resultobtained by diagnostic unit 16 to information terminal 70 using radior2, for example.

As shown in FIG. 29 , lighting device 10D has housing 29, which is ahousing case. Communication unit 11, light emitter 12, detector 13,controller 15, and diagnostic unit 16 are provided in housing 29 or onan outer surface of housing 29. Housing 29 is fixed to pole body 23 witha ring member or a fastener member, for example. Communication unit 11,light emitter 12, detector 13, controller 15, and diagnostic unit 16 maybe housed in pole body 23, rather than in housing 29, or may be providedin a notch or hole formed on pole body 23.

Housing 29 is provided at an upper part of pole body 23, for example, ata height of at least 4.5 m and at most 15 m from the ground surface ofparking space 91. Housing 29 has a rectangular parallelepiped shape, forexample, and is made of metal, resin or other materials.

Light emitter 12 emits illumination light to vehicle 50 or parking space91. Light emitter 12 is a liquid crystal projector that projects astatic image or moving image, or an LED light emitting module that emitswhite light. Light emitter 12 may be a combination of separate SMDs andCOBs of RGB, incandescent bulb color, neutral white color or othercolors. When light emitter 12 is a liquid crystal projector, lightingdevice 10D can notify information regarding the hacking of vehicle 50 byusing a static image or moving image.

Detector 13 is a sensor that detects vehicle 50 in parking space 91.Detector 13 is an image sensor, an infrared sensor, or a laser sensor,for example. Detector 13 is constantly operating, and constantly detectsthe presence or absence of vehicle 50 in a predetermined area of parkingspace 91. Detection information from detector 13 is output to controller15.

Controller 15 is a circuit that controls operations of communicationunit 11, light emitter 12, detector 13, and diagnostic unit 16.Controller 15 is formed by a microprocessor, memory 15 a, and a programstored in memory 15 a, for example. Memory 15 a stores identificationinformation on information terminal 70.

When detector 13 detects vehicle 50 capable of autonomous driving,controller 15 issues a diagnosis command to diagnostic unit 16 to startdiagnosis of vehicle 50.

Instead of using detector 13 to detect whether or not vehicle 50 isautonomously driving, controller 15 may establish a communication withvehicle 50, which is triggered by visible light communication from lightemitter 12 to vehicle 50, and obtain information for determining whetheror not vehicle 50 is autonomously driving. Alternatively, instead ofusing detector 13 to detect whether or not vehicle 50 is autonomouslydriving, controller 15 may determine whether or not vehicle 50autonomously driving by requesting for information for determiningwhether or not vehicle 50 is autonomously driving from parked vehicle 50by regularly transmitting a beacon signal from communication unit 11.

Diagnostic unit 16 is a circuit that diagnoses, via communication unit11, whether vehicle 50 is being hacked. Diagnostic unit 16 performsdiagnosis of the presence of hacking when light emitter 12 is in the offstate or on state, and diagnostic unit 16 has received a diagnosiscommand from controller 15, for example.

There are three examples of the vehicle diagnosis by diagnostic unit 16.

A first diagnosis example is an example in which a vehicle diagnosis isperformed based on an answer to a question asked to vehicle 50 bylighting device 10D. Diagnostic unit 16 asks vehicle 50 a plurality ofquestions, and determines whether vehicle 50 is being hacked based on atleast one of the answering time or the answer tendency to the questions.

A second diagnosis example is an example in which a vehicle diagnosis isperformed by checking the resilience of software that runs a travelsystem provided in vehicle 50. Diagnostic unit 16 checks the resilienceof the software in vehicle 50 via communication unit 11, and diagnosesthat vehicle 50 is being hacked when the resilience level is lower thana predetermined level.

A third diagnosis example is an example in which an operation log ofvehicle 50 is obtained, and a vehicle diagnosis is performed based onthe operation log. Diagnostic unit 16 obtains the operation log ofvehicle 50 via communication unit 11, and diagnoses that vehicle 50 hasbeen hacked when vehicle 50 is not following a predetermined operationalregulation.

When diagnostic unit 16 has diagnosed that vehicle 50 is being hacked,controller 15 notifies information terminal 70 that vehicle 50 is beinghacked.

Information terminal 70 is a terminal, such as a smartphone, a tabletterminal, or a personal computer (PC). Application software for browsinginformation on the diagnosis result of vehicle 50 is installed ininformation terminal 70. Information terminal 70 obtains information onthe diagnosis result from lighting device 10D by radio r2, and displaysthe information on a screen.

The owner having obtained information on the diagnosis result frominformation terminal 70 can immediately take measures to cope with thehacked vehicle 50. In this way, damage due to the hacking of vehicle 50can be reduced.

In another example of the notification of the diagnosis result, lightingsystem 1D may notify a computer communicatively connected to lightingsystem 1D via a network of the diagnosis result (see FIG. 28 ). Forexample, lighting system 1D may transmit the diagnosis result to amanagement server that is a computer owned by a dealer of vehicle 50.Lighting system 1D may also notify of the diagnosis result bytransmitting an e-mail to an e-mail address registered by the owner ordealer in advance. This allows the owner or dealer to take measures tocope with the hacked vehicle 50 and reduce damage due to the hacking ofvehicle 50.

[5-2. Operation of Lighting System]

Next, an operation of lighting system 1D according to Embodiment 5 willbe described,

FIG. 30 is a flowchart illustrating an example of an operation oflighting system 1D.

First, the owner of vehicle 50 parks vehicle 50 in parking space 91(Step S41).

After vehicle 50 is parked in parking space 91, when the owner holdinginformation terminal 70 leaves a predetermined distance or more fromparking space 91 (Step S42), lighting system 1D starts diagnosis ofvehicle 50 (Step S43). The predetermined distance is a distance from anentrance/exit of parking space 91 to a different place than parkingspace 91 or a passage, and is greater than or equal to 5 m or greaterthan or equal to 10 m, for example. Lighting system 1D can obtaininformation on whether the owner has left parking space 91 thepredetermined distance or more from parking space 91 by loading positioninformation on information terminal 70.

When the owner comes within a predetermined distance from parking space91 in order to use vehicle 50 (Step S44), lighting system 1D ends thediagnosis of vehicle 50 (Step S45). When ending the vehicle diagnosis,lighting system 1D records the diagnosis result in memory 15 a. Withlighting system 1D, the presence of hacking of vehicle 50 can bediagnosed at an opportunity where vehicle 50 is parked in parking space91. In this way, damage due to the hacking of vehicle 50 can be reduced.

Embodiment 6

A configuration of lighting system 1E according to Embodiment 6 will bedescribed with reference to FIG. 31 to FIG. 32 . In Embodiment 6, anexample will be described in which vehicle 50 that is traveling, vehicle50 that is stopped, and vehicle 50 that is parked are diagnosed.

FIG. 31 is a schematic diagram illustrating lighting system 1E. As shownin FIG. 31 , Lighting system 1E includes a plurality of lighting devices10E provided at a side of road 92 and parking space 91, and vehiclediagnostic device 30E communicatively connected to the plurality oflighting devices 10E via network N, such as the Internet. FIG. 31 alsoillustrates information terminal 70 communicatively connected to vehiclediagnostic device 30E via network N.

Lighting device 10E is a device that emits illumination light to road 92and parking space 91, and is an outdoor lighting device, such as astreet light or a security light.

Lighting device 10E includes pole body 23 installed at a side of road 92or parking space 91, and lamp 22 provided on pole body 23.

Pole body 23 is a columnar member, and is a utility pole on which adistribution line is provided, a pole of a street light, or a pole towhich a security camera is attached, for example. Pole body 23 may havean L-shape or T-shape. A plurality of pole bodies 23 are arranged atpredetermined intervals, such as intervals of at least 20 m and at most50 m, along an edge of road 92, and a plurality of lamps 22 are alsoarranged at the same predetermined intervals.

FIG. 32 is a block diagram illustrating a configuration of lightingsystem 1E. FIG. 32 also illustrates a computer communicatively connectedto lighting system 1E via a network.

As shown in FIG. 32 , lighting device 10E includes communication unit11, light emitter 12, detector 13, and controller 15. Vehicle diagnosticdevice 30E includes controller 35 and diagnostic unit 36.

Communication unit 11 is a communication module that communicates withvehicle 50 by radio r1, and communicates with vehicle diagnostic device30E by wire. Communication unit 11 transmits detection information fromdetector 13 to vehicle diagnostic device 30E via network N, for example.

Lamp 22 has housing 29, which is a housing case. Communication unit 11,light emitter 12, detector 13, and controller 15 are provided in housing29 or on an outer surface of housing 29. Housing 29 is fixed to polebody 23 with a ring member or a fastener member, for example.Communication unit 11, light emitter 12, detector 13, and controller 15may be housed in pole body 23, rather than in housing 29, or may beprovided in a notch or hole formed on pole body 23.

Housing 29 is provided at an upper part of pole body 23, for example, ata height of at least 4.5 m and at most 15 m from the ground surface ofroad 92. Housing 29 has a rectangular parallelepiped shape, for example,and is provided on pole body 23 so as to protrude toward the center ofroad 92 from pole body 23. Housing 29 is made of metal, resin or othermaterials.

Light emitter 12 emits illumination light to road 92, parking space 91,and vehicle 50. Light emitter 12 is a liquid crystal projector thatprojects a static image or moving image, or an LED light emitting modulethat emits white light. Light emitter 12 may be a combination ofseparate SMDs and COBs RGB, incandescent bulb color, neutral white coloror other colors. When light emitter 12 is a liquid crystal projector,lighting device 10E can notify information regarding the hacking ofvehicle 50 by using a static image or moving image.

Detector 13 is a sensor that detects vehicle 50 on road 92 or in parkingspace 91. Detector 13 is provided in each of a plurality of pole bodies23 installed along road 92 and a plurality of pole bodies 23 installedin parking space 91 as shown in FIG. 31 . Detector 13 is an imagesensor, an infrared sensor, or a laser sensor, for example. Detector 13is constantly operating, and constantly detects the presence or absenceof vehicle 50 in a predetermined area of road 92 or parking space 91.Detection information from detector 13 is output to vehicle diagnosticdevice 30E via controller 15 and communication unit 11.

Controller 15 of lighting device 10E is a circuit that controlsoperations of communication unit 11, light emitter 12, and detector 13.Controller 15 is formed by a microprocessor, memory 15 a, and a programstored in memory 15 a, for example.

Controller 35 of vehicle diagnostic device 30E is formed by amicroprocessor, memory 35 a, and a program stored in memory 35 a, forexample. Memory 35 a stores identification information on vehicle 50,such as a license plate number. An operation log and a diagnosis resultof vehicle 50 are also recorded in memory 35 a.

When detector 13 detects vehicle 50 capable of autonomous driving andcontroller 35 obtains the detection information via network N,controller 35 issues a diagnosis command to diagnostic unit 36 to startdiagnosis of vehicle 50.

Controller 35 may use detector 13 to determine whether vehicle 50 istraveling, stopped, or parked. Controller 35 may also use anacceleration sensor or the like provided in vehicle 50 to determinewhether vehicle 50 is traveling, stopped, or parked.

Instead of using detector 13 to detect whether or not vehicle isautonomously driving, controller 35 may establish a communication withvehicle 50, which is triggered by visible light communication from lightemitter 12 to vehicle 50, and obtain information for determining whetheror not vehicle 50 is autonomously driving. Alternatively, instead ofusing detector 13 to detect whether or not vehicle 50 is autonomouslydriving, controller 35 may determine whether or not vehicle 50 isautonomously driving by requesting for information for determiningwhether or not vehicle 50 is autonomously driving from traveling orparked vehicle 50 by regularly transmitting a beacon signal fromcommunication unit 11.

Diagnostic unit 36 is a circuit that diagnoses, via network N andcommunication unit 11, whether vehicle 50 is being hacked. Whendiagnostic unit 36 has received a diagnosis command from controller 35,for example, diagnostic unit 36 performs transmission and reception ofdata between diagnostic unit 36 and vehicle 50 via network N andcommunication unit 11 and performs diagnosis the presence of hacking ofvehicle 50 based on the transmitted and received data. When diagnosingthe presence of hacking of traveling vehicle 50, diagnostic unit 36 mayperform the diagnosis by sequentially changing from one lighting device10E to another lighting device 10E of the plurality of lighting devices10E to communicate with vehicle 50.

There are three examples of the vehicle diagnosis by diagnostic unit 36.

A first diagnosis example is an example in which a vehicle diagnosis isperformed based on an answer to a question asked to vehicle 50 bylighting device 10E. Diagnostic unit 36 asks vehicle 50 a plurality ofquestions via lighting device 10E, and determines whether vehicle 50 isbeing hacked based on at least one of the answering time or the answertendency to the questions.

A second diagnosis example is an example in which a vehicle diagnosis isperformed by checking the resilience of software that runs a travelsystem provided in vehicle 50. Diagnostic unit 36 checks the resilienceof the software in vehicle 50 via communication unit 11 of lightingdevice 10E, and diagnoses that vehicle 50 is being hacked when theresilience level is lower than a predetermined level.

A third diagnosis example is an example in which an operation log ofvehicle 50 is obtained, and a vehicle diagnosis is performed based onthe operation log. Diagnostic unit 36 obtains the operation log ofvehicle 50 via communication unit 11 of lighting device 10E, anddiagnoses that vehicle 50 has been hacked when vehicle 50 is notfollowing a predetermined operational regulation.

When diagnostic unit 36 has diagnosed that vehicle 50 is being hacked,controller 35 notifies information terminal 70 that vehicle 50 is beinghacked.

Information terminal 70 is a terminal, such as a smartphone, a tabletterminal, or a PC. Application software for browsing information on thediagnosis result of vehicle 50 is installed in information terminal 70.Information terminal 70 obtains information on the diagnosis result vianetwork N, and displays the information on a screen.

The owner having obtained information on the diagnosis result frominformation terminal 70 can immediately take measures to cope with thehacked vehicle 50. In this way, damage due to the hacking of vehicle 50can be reduced.

In another example of the notification of the diagnosis result, lightingsystem 1E may notify a computer communicatively connected to lightingsystem 1E via network N of the diagnosis result (see FIG. 32 ). Forexample, lighting system 1E may transmit the diagnosis result to amanagement server that is a computer owned by a dealer of vehicle 50.Lighting system 1E may also notify of the diagnosis result bytransmitting an e-mail to an e-mail address registered by the owner ordealer in advance. This allows the owner or dealer to take measures tocope with the hacked vehicle 50 and reduce damage due to the hacking ofvehicle 50.

FIG. 33 is a diagram illustrating an example of operations of lightingsystem 1E. FIG. 33 illustrates that the amount of data and the timing ofcommunication of the communication with vehicle 50 vary depending onwhether vehicle 50 is parked, stopped, or traveling. That is, in thediagnosis by diagnostic unit 36 of lighting system 1E, at least one ofthe duration of diagnosis or the amount of diagnosis varies depending onwhether vehicle 50 is parked, stopped, or traveling.

For example, when diagnostic unit 36 has determined that vehicle 50 isparked, diagnostic unit 36 may perform diagnosis by setting at least oneof the duration of diagnosis or the amount of diagnosis to be greaterthan when vehicle 50 is traveling or stopped. When diagnostic unit 36has determined that vehicle 50 is stopped, diagnostic unit 36 mayperform diagnosis by setting at least one of the duration of diagnosisor the amount of diagnosis to be greater than when vehicle 50 istraveling and setting at least one of the duration of diagnosis or theamount of diagnosis to be smaller than when vehicle 50 is parked. Whendiagnostic unit 36 has determined that vehicle 50 is traveling,diagnostic unit 36 may perform diagnosis by setting at least one of theduration of diagnosis or the amount of diagnosis to be smaller than whenvehicle 50 is stopped or parked.

For example, when vehicle 50 is parked, a longer duration of diagnosisand a larger amount of diagnosis can be secured, so that of the threediagnosis examples described above, the diagnosis based on questions andanswers exchanged with the vehicle, the diagnosis based on theresilience check, or the diagnosis based on the operation log isperformed. When vehicle 50 is stopped, the duration of diagnosis and theamount of diagnosis have to be reduced compared with when the vehicle isparked, only the diagnosis based on questions and answers or thediagnosis based on the resilience check is performed, and the diagnosisbased on the operation log is not performed. When vehicle 50 istraveling, the duration of diagnosis and the amount of diagnosis have tobe reduced compared with when the vehicle is stopped, the number ofquestions and answers exchanged with the vehicle, or the amount of datatransmitted and received for checking the resilience or the number ofdata transmissions and receptions for checking the resilience is reducedcompared with when the vehicle is stopped. When vehicle 50 is traveling,the diagnosis based on the operation log is not performed.

In this way, vehicle 50 can be appropriately diagnosed when vehicle 50is parked, stopped, and traveling.

Embodiment 7

A configuration of lighting device 10F according to Embodiment 7 will bedescribed with reference to FIG. 34 and FIG. 35 . In Embodiment 7, anexample will be described in which not only vehicle 50 but also mobilebody 80, such as an unmanned aircraft, is diagnosed.

FIG. 34 is a diagram illustrating an example installation of lightingdevice 10F according to Embodiment 7.

Lighting device 10F is installed in waiting area 96 in which mobile body80 is waiting, and emits illumination light to mobile body 80 andwaiting area 96. Although lighting device 10F is installed on anexterior wall of a takeoff and landing site, which is an example ofbuilding 60, in FIG. 34 , the present disclosure is not limited to this,and lighting device 10F may be installed on a roof, a fence, a pillar orthe like of the takeoff and landing site.

Mobile body 80 is an unmanned aircraft capable of autonomous driving,such as a drone or other air vehicles. The autonomous driving means thatthe mobile body drives autonomously and includes not only unmanneddriving but also that the driver is assisted in manipulating the mobilebody. Mobile body 80 may be an air vehicle that can switch between amanual driving mode and an autonomous driving mode. Mobile body 80 isprovided with communication antenna 81 for communicating with lightingdevice 10F and camera 82 that recognizes illumination light fromlighting device 10F. Mobile body 80 has an AI assistant function.

FIG. 35 is a block diagram illustrating a configuration of lightingdevice 10F. FIG. 35 also illustrates a computer communicativelyconnected to lighting device 10F via a network.

As shown in FIG. 35 , lighting device 10F includes communication unit 11that communicates with mobile body 80, light emitter 12 that can emitillumination light, detector 13 that detects mobile body 80, anddiagnostic unit 16 that diagnoses mobile body 80 as to whether anautonomous driving program of mobile body 80 is being hacked. Lightingdevice 10F further includes controller 15 that controls turning on andoff, dimming, and toning of light emitter 12.

Light emitter 12 is a light source that emits illumination light, and isa liquid crystal projector that projects a static image or moving imageor an LED light emitting module that emits light of red color, greencolor, or blue color, or synthetic light of these colors, for example.Light emitter 12 may be a combination of separate SMDs and COBs of RGB,incandescent bulb color, neutral white color, or other colors. Lightemitter 12 is provided at a position higher than the height of mobilebody 80 waiting on the ground, in order to illuminate mobile body 80 andsurroundings of mobile body 80.

Detector 13 is a sensor that detects the presence or absence of mobilebody 80 in waiting area 96, such as an image sensor, an infrared sensor,or a laser sensor. Detector 13 is constantly operating, and detectswhether mobile body 80 is waiting in waiting area 96. In the presentembodiment, light emitter 12 is turned on in response to detector 13detecting mobile body 80, and diagnostic unit 16 is enabled to diagnosemobile body 80 in response to turning on of light emitter 12.

Communication unit 11 is a communication module that communicates withmobile body 80 by radio r1. The communication scheme based on radio r1may be Bluetooth®, a specified low power radio using a frequency in the920 MHz band, Zigbee®, or WiFi®, for example.

Controller 15 is formed by a microprocessor, memory 15 a, and a programstored in memory 15 a, for example. Memory 15 a stores identificationinformation on mobile body 80, such as a mobile body number. Anoperation log and a diagnosis result of mobile body 80 described laterare also recorded in memory 15 a. Controller 15 controls turning on andthe like of light emitter 12, and controls operations of communicationunit 11, detector 13, and diagnostic unit 16.

When detector 13 detects mobile body 80, for example, controller 15transmits, to mobile body 80, a request signal that requests for theidentification information on mobile body 80 via communication unit 11.Controller 15 issues a diagnosis command to diagnostic unit 16 to makediagnostic unit 16 diagnose mobile body 80, when the identificationinformation on mobile body 80 transmitted from mobile body 80 agreeswith identification information registered in advance.

Instead of transmitting the request signal described above, controller15 may establish a communication with mobile body 80, which is triggeredby visible light communication from light emitter 12 to mobile body 80,and obtain the identification information on mobile body 80. Controller15 may obtain the identification information on mobile body 80 byimaging the mobile body number plate by means of detector 13. Instead ofusing detector 13, controller 15 may obtain the identificationinformation on mobile body 80 by requesting for transmission of theidentification information from mobile body 80 by regularly transmittinga beacon signal from communication unit 11. That is, controller 15 maydetect mobile body 80 by means of communication unit 11 and then performdiagnosis via communication unit 11.

Diagnostic unit 16 is a circuit that diagnoses, via communication unit11, whether mobile body 80 is being hacked. When the lighting state oflight emitter 12 changes, for example, diagnostic unit 16 performsdiagnosis of mobile body 80 waiting in waiting area 96. Specifically,diagnostic unit 16 performs diagnosis of the presence of hacking ofmobile body 80 when light emitter 12 changes from the off state to theon state and diagnostic unit 16 has received a diagnosis command fromcontroller 15.

Diagnostic unit 16 may perform diagnosis of the presence of hacking ofmobile body 80 not only when light emitter 12 changes from the off stateto the on state but also when light emitter 12 changes from the on stateto the off state or the dimmed state or when the lighting color changes.Furthermore, diagnostic unit 16 may end the diagnosis of the presence ofhacking of mobile body 80 when the lighting state changes again afterlight emitter 12 changes from the on state to the off state or thedimmed state or after the lighting color changes. Note that the dimmedstate is a state in which a toning control is being performed so thatthe brightness of the light is less than or equal to a predeterminedbrightness, for example, a state where the lighting is controlled sothat the illuminance is 30%. That the lighting color changes means astate where a toning control is performed so that the color temperaturechanges.

There are three examples of the diagnosis of mobile body 80 bydiagnostic unit 16, which are the same as those described above.

A first diagnosis example is an example in which diagnosis of mobilebody 80 is performed based on an answer to a question asked to mobilebody 80 by lighting device 10F. Diagnostic unit 16 asks mobile body 80 aplurality of questions, and determines whether mobile body 80 is beinghacked based on at least one of the answering time or the answertendency to the questions.

A second diagnosis example is an example in which diagnosis of mobilebody 80 is performed by checking the resilience of software that runs atravel system (flight system) provided in mobile body 80. Diagnosticunit 16 checks the resilience of the software in mobile body 80 viacommunication unit 11, and diagnoses that mobile body 80 is being hackedwhen the resilience level is lower than a predetermined level.

A third diagnosis example is an example in which an operation log(flight record) of mobile body 80 is obtained, and diagnosis of mobilebody 80 is performed based on the operation log. Diagnostic unit 16obtains the operation log of mobile body 80 via communication unit 11,and diagnoses that mobile body 80 has been hacked when mobile body 80 isnot following a predetermined operational regulation.

When diagnostic unit 16 has diagnosed that mobile body 80 is beinghacked, controller 15 notifies of the hacking of mobile body 80 usingillumination light from light emitter 12. For example, when lightemitter 12 is a liquid crystal projector, controller 15 notifiesinformation regarding hacking by illuminating mobile body 80 or waitingarea 96 with a static image or moving image projected by light emitter12.

In this way, a user of mobile body 80 can visually know whether mobilebody 80 is being hacked. Therefore, the user can take measures to copewith the hacked mobile body 80, and reduce damage due to the hacking ofmobile body 80.

In another example of the notification of the diagnosis result, lightingdevice 10F may notify a computer communicatively connected to lightingdevice 10F via a network of the diagnosis result (see FIG. 35 ). Forexample, lighting device 10F may transmit the diagnosis result to amanagement server that is a computer owned by a dealer of mobile body80. Lighting device 10F may also notify of the diagnosis result bytransmitting an e-mail to an e-mail address registered by the owner ordealer in advance. This allows the owner or dealer to take measures tocope with the hacked mobile body 80 and reduce damage due to the hackingof mobile body 80.

Embodiment 8

A configuration of lighting system 1G according to Embodiment 8 will bedescribed with reference to FIG. 36 and FIG. 37 . In Embodiment 8, anexample will be described in which mobile body 80 that is moving, mobilebody 80 that is stopped, and mobile body 80 that is waiting arediagnosed.

FIG. 36 is a schematic diagram illustrating lighting system 1G accordingto Embodiment 8. FIG. 36 illustrates a plurality of mobile bodies 80flying along travel path 97 above a road, and a plurality of mobilebodies 80 having landed in waiting area 96 provided outside the road.

Lighting system 1G according to Embodiment 8 includes a plurality oflighting devices 10G, and mobile body diagnostic device 30Gcommunicatively connected to the plurality of lighting devices 10G vianetwork N, such as the Internet. FIG. 36 also illustrates informationterminal 70 communicatively connected to mobile body diagnostic device30G via network N.

Lighting device 10G is a device that emits illumination light to road 92that is parallel with travel path 97 along which mobile body 80 moves,and waiting area 96 in which mobile body 80 is waiting, and is anoutdoor lighting device, such as a street light or a security light.

Lighting device 10G includes pole body 23 installed at a side of road 92below travel path 97 or waiting area 96, and lamp 22 provided on polebody 23.

Pole body 23 is a columnar member, and is a utility pole on which adistribution line is provided, a pole of a street light, or a pole towhich a security camera is attached, for example. Pole body 23 may havean L-shape or T-shape. A plurality of pole bodies 23 are arranged atpredetermined intervals, such as intervals of at least 20 m and at most50 m, along an edge of road 92, and a plurality of lamps 22 are alsoarranged at the same predetermined intervals. Mobile body 80 may selecttravel path 97 based on light emitted by a plurality of lamps 22.

FIG. 37 is a block diagram illustrating a configuration of lightingsystem 1G. FIG. 37 also illustrates a computer communicatively connectedto lighting system 1G via a network.

As shown in FIG. 37 , lighting device 10G includes communication unit11, light emitter 12, detector 13, and controller 15. Mobile bodydiagnostic device 30G includes controller 35 and diagnostic unit 36.

Communication unit 11 is a communication module that communicates withmobile body 80 by radio r1, and communicates with mobile body diagnosticdevice 30G by wire. Communication unit 11 transmits detectioninformation from detector 13 to mobile body diagnostic device 30G vianetwork N, for example.

Lamp 22 has housing 29, which is a housing case. Communication unit 11,light emitter 12, detector 13, and controller 15 are provided in housing29 or on an outer surface of housing 29. Housing 29 is fixed to polebody 23 with a ring member or a fastener member, for example.Communication unit 11, light emitter 12, detector 13, and controller 15may be housed in pole body 23, rather than in housing 29, or may beprovided in a notch or hole formed on pole body 23.

Housing 29 is provided at an upper part of pole body 23 that is lowerthan travel path 97 of mobile body 80. Housing 29 has a rectangularparallelepiped shape, for example, and is provided on pole body 23 so asto protrude toward the center of travel path 97 from pole body 23.Housing 29 is made of metal, resin or other materials.

Light emitter 12 emits illumination light to road 92 that is parallelwith travel path 97, waiting area 96, or mobile body 80. Light emitter12 is a liquid crystal projector that projects a static image or movingimage, or an LED light emitting module that emits white light. Lightemitter 12 may be a combination of separate RGB, incandescent, neutralor other SMDs and COBs. When light emitter 12 is a liquid crystalprojector, lighting device 10G can notify information regarding thehacking of mobile body 80 by using a static image or moving image.

Detector 13 is a sensor that detects mobile body 80 on travel path 97 orin waiting area 96. Detector 13 is provided in each of a plurality ofpole bodies 23 installed along travel path 97 and road 92 and aplurality of pole bodies 23 installed in waiting area 96 as shown inFIG. 36 . Detector 13 is an image sensor, an infrared sensor, or a lasersensor, for example. Detector 13 is constantly operating, and constantlydetects the presence or absence of mobile body 80 in a predeterminedarea of travel path 97 or waiting area 96. Detection information fromdetector 13 is output to mobile body diagnostic device 30G viacontroller 15 and communication unit 11.

Controller 15 of lighting device 10G is a circuit that controlsoperations of communication unit 11, light emitter 12, and detector 13.Controller 15 is formed by a microprocessor, memory 15 a, and a programstored in memory 15 a, for example.

Controller 35 of mobile body diagnostic device 30G is formed by amicroprocessor, memory 35 a, and a program stored in memory 35 a, forexample. Memory 35 a stores identification information on mobile body80, such as a mobile body number. An operation log and a diagnosisresult of mobile body 80 are also recorded in memory 35 a.

When detector 13 detects mobile body 80 capable of autonomous driving,and controller 35 receives the detection information via network N,controller 35 issues a diagnosis command to diagnostic unit 36 to startdiagnosis of mobile body 80.

Controller 35 may use detector 13 to determine whether mobile body 80 ismoving, stopped, or waiting. Controller 35 may also use an accelerationsensor or the like provided in mobile body 80 to determine whethermobile body 80 is moving, stopped, or waiting.

Instead of using detector 13 to detect whether or not mobile body 80 isautonomously driving, controller 35 may establish a communication withmobile body 80, which is triggered by visible light communication fromlight emitter 12 to mobile body 80, and obtain information fordetermining whether or not mobile body 80 is autonomously driving.Alternatively, instead of using detector 13 to detect whether or notmobile body 80 is autonomously driving, controller 35 may determinewhether or not mobile body 80 is autonomously driving by requesting forinformation for determining whether or not mobile body 80 isautonomously driving from moving or waiting mobile body 80 by regularlytransmitting a beacon signal from communication unit 11.

Diagnostic unit 36 is a circuit that diagnoses, via network N andcommunication unit 11, whether mobile body 80 is being hacked. Whendiagnostic unit 36 has received a diagnosis command from controller 35,for example, diagnostic unit 36 performs transmission and reception ofdata between diagnostic unit 36 and mobile body 80 via network N andcommunication unit 11 and performs diagnosis of the presence of hackingof mobile body based on the transmitted and received data. Whendiagnosing the presence of hacking of moving mobile body 80, diagnosticunit 36 may perform the diagnosis by sequentially changing from onelighting device 10G to another lighting device 10G of the plurality oflighting devices 10G to communicate with mobile body 80.

There are three examples of the diagnosis of mobile body 80 bydiagnostic unit 36, which are the same as those described above.

A first diagnosis example is an example in which diagnosis of mobilebody 80 is performed based on an answer to a question asked to mobilebody 80 by lighting device 10G. Diagnostic unit 36 asks mobile body 80 aplurality of questions via lighting device 10G, and determines whethermobile body 80 is being hacked based on at least one of the answeringtime or the answer tendency to the questions.

A second diagnosis example is an example in which diagnosis of mobilebody 80 is performed by checking the resilience of software that runs atravel system provided in mobile body 80. Diagnostic unit 36 checks theresilience of the software in mobile body 80 via communication unit 11of lighting device 10G, and diagnoses that mobile body 80 is beinghacked when the resilience level is lower than a predetermined level.

A third diagnosis example is an example in which an operation log(flight record) of mobile body 80 is obtained, and diagnosis of mobilebody 80 is performed based on the operation log. Diagnostic unit 36obtains the operation log of mobile body 80 via communication unit 11 oflighting device 10G, and diagnoses that mobile body 80 has been hackedwhen mobile body 80 is not following a predetermined operationalregulation.

When diagnostic unit 36 has diagnosed that mobile body 80 is beinghacked, controller 35 notifies information terminal 70 that mobile body80 is being hacked.

Information terminal 70 is a terminal, such as a smartphone, a tabletterminal, or a PC. Application software for browsing information on thediagnosis result of mobile body 80 is installed in information terminal70. Information terminal 70 obtains information on the diagnosis resultvia network N, and displays the information on a screen.

The owner having obtained information on the diagnosis result frominformation terminal 70 can immediately take measures to cope with thehacked mobile body 80. In this way, damage due to the hacking of mobilebody 80 can be reduced.

In another example of the notification of the diagnosis result, lightingsystem 1G may notify a computer communicatively connected to lightingsystem 1G via network N of the diagnosis result (see FIG. 37 ). Forexample, lighting system 1G may transmit the diagnosis result to amanagement server that is a computer owned by a dealer of mobile body80. Lighting system 1G may also notify of the diagnosis result bytransmitting an e-mail to an e-mail address registered by the owner ordealer in advance. This allows the owner or dealer to take measures tocope with the hacked mobile body 80 and reduce damage due to the hackingof mobile body 80.

SUMMARY

As described above, lighting device 10 according to the foregoingembodiments includes: communication unit 11 that communicates withvehicle 50 which drives autonomously; diagnostic unit 16 that performs,via communication unit 11, diagnosis as to whether vehicle 50 is beinghacked; and light emitter 12 that emits illumination light onto at leastone of vehicle 50, road 92 on which vehicle 50 travels, or parking space91 in which vehicle 50 parks.

Since lighting device 10 can diagnose whether vehicle 50 is beinghacked, damage due to the hacking of vehicle 50 can be reduced.

Furthermore, diagnostic unit 16 may perform the diagnosis on vehicle 50which is parked in parking space 91, when a lighting state of lightemitter 12 changes.

Accordingly, triggered by a change that occurs in daily life, such asthe changing of the lighting state of light emitter 12, it is possibleto diagnose whether vehicle 50 is being hacked. Furthermore, sincevehicle 50 is parked in parking space 91, sufficient diagnosis over along time can be performed. With this, damage due to the hacking ofvehicle 50 can be reduced. Moreover, since the diagnosis can be madeaccording to the changing of the lighting state of light emitter 12, thetrouble that the user has to go through in order to start the diagnosisof vehicle 50 can be reduced.

Furthermore, diagnostic unit 16 may perform the diagnosis when lightemitter 12 changes from an on state to an off state or a dimmed state orchanges lighting color.

Accordingly, triggered by a change that occurs in daily life, such aslight emitter 12 changing from the on state to the off state or a dimmedstate, or changing lighting color, it is possible to diagnose whethervehicle 50 is being hacked. Furthermore, since vehicle 50 is not drivenover a long time when light emitter 12 has changed to the off state orthe dimmed state, or has changed lighting color, sufficient diagnosisover a long time can be performed. With this, damage due to the hackingof vehicle 50 can be reduced.

Furthermore, diagnostic unit 16 may end the diagnosis when the lightingstate of light emitter 12 changes again after changing from the on stateto the off state or the dimmed state, or after changing the lightingcolor.

As described above, by ending the diagnosis when the lighting state oflight emitter 12 changes again, diagnosis of the hacking of vehicle 50can be made a part of the changes in daily life. With this, damage dueto the hacking of vehicle 50 can be reduced.

Furthermore, communication unit 11 may start communication with vehicle50, with visible light communication from light emitter 12 to vehicle 50as a trigger.

Accordingly, since a trigger for communication between communicationunit 11 and vehicle 50 can be certainly created, diagnosis of vehicle 50which makes use of communication can be certainly performed. With this,damage due to the hacking of vehicle 50 can be reduced.

Furthermore, when diagnostic unit 16 diagnoses that vehicle 50 is beinghacked, light emitter 12 may notify that vehicle 50 is being hacked, byusing an illumination light of light emitter 12.

Accordingly, a user of vehicle 50 can visually know whether vehicle 50is being hacked. With this, the user can take measures to cope withvehicle 50 that has been hacked, and thus damage due to the hacking ofvehicle 50 can be reduced.

Furthermore, light emitter 12 may perform the notification by projectingthe illumination light onto at least one of vehicle 50 or parking space91.

Accordingly, a user of vehicle 50 can know with certainty whethervehicle 50 is being hacked. With this, the user can take measures tocope with vehicle 50 that has been hacked and thus damage due to thehacking of vehicle 50 can be reduced.

Furthermore, when diagnostic unit 16 diagnoses that vehicle 50 is beinghacked, lighting device 10 may notify a computer communicativelyconnected to lighting device 10 that vehicle 50 is being hacked.

Accordingly, a user of vehicle 50 can, through a computer, know withcertainty whether vehicle 50 is being hacked. With this, the user cantake measures to cope with vehicle 50 that has been hacked and thusdamage due to the hacking of vehicle 50 can be reduced.

Furthermore, when diagnostic unit 16 diagnoses that vehicle 50 is beinghacked, lighting device 10 may notify that vehicle 50 is being hacked,by sending an electronic mail to a pre-registered mail address.

Accordingly, a user having the registered mail address can, throughelectronic mail, know with certainty whether vehicle 50 is being hacked.With this, the user can take measures to cope with vehicle 50 that hasbeen hacked and thus damage due to the hacking of vehicle 50 can bereduced.

Furthermore, diagnostic unit 16 may perform the diagnosis based on ananswer to a question to vehicle 50.

Accordingly, it is possible to diagnose whether vehicle 50 is beinghacked, based on the answer to the question. With this, damage due tothe hacking of vehicle 50 can be reduced.

Furthermore, diagnostic unit 16 may perform the diagnosis based on atleast one of an answering time or an answering tendency to a pluralityof questions.

Accordingly, it is possible to appropriately diagnose whether vehicle 50is being hacked. With this, damage due to the hacking of vehicle 50 canbe reduced.

Furthermore, diagnostic unit 16 may ask vehicle 50 a question having auniquely-determined answer via communication unit 11, and diagnose thatvehicle 50 is being hacked when the answering time to the question isslower than a predetermined time.

Accordingly, it is possible to easily diagnose whether vehicle 50 isbeing hacked. With this, damage due to the hacking of vehicle 50 can bereduced.

Furthermore, diagnostic unit 16 may ask vehicle 50 questions havinganswers that are non-uniquely-determined via communication unit 11, anddiagnose that vehicle 50 is being hacked when an amount of variation inthe answers to the questions is smaller than a predetermined amount ofvariation.

Accordingly, it is possible to diagnose, with an advanced perspective,whether vehicle 50 is being hacked. With this, damage due to the hackingof vehicle 50 can be reduced.

Furthermore, diagnostic unit 16 may perform the diagnosis by checkingresilience of software which runs a travel system provided in vehicle50, via communication unit 11.

Accordingly, it is possible to diagnose whether vehicle 50 is beinghacked, based on the resilience of the software. With this, damage dueto the hacking of vehicle 50 can be reduced.

Furthermore, diagnostic unit 16 may diagnose that vehicle 50 is beinghacked when a level of the resilience of the software is lower than apredetermined level.

Accordingly, it is possible to certainly diagnose whether vehicle 50 isbeing hacked. With this, damage due to the hacking of vehicle 50 can bereduced.

Furthermore, diagnostic unit 16 may check the resilience of the softwareby performing at least one of a denial-of-service (DoS) attack or abuffer overflow attack on the software.

Accordingly, it is possible to prevent a hacker from hacking vehicle 50.With this, damage due to the hacking of vehicle 50 can be reduced.

Furthermore, when the DoS attack causes the level of the resilience ofthe software to become lower than the predetermined level, diagnosticunit 16 may continue the DoS attack until the software ceases tofunction.

Accordingly, since it is possible to cause the loss of the travelfunction of vehicle 50, damage due to the hacking of vehicle 50 can bereduced.

Furthermore, diagnostic unit 16 may check the resilience of the softwareby performing transmission of trap data to the software.

Accordingly, the hacker performing the hacking can be lured out. Withthis, it is possible to reduce damage due to the hacking of vehicle 50.

Furthermore, when a backdoor to the software is found through thetransmission of the trap data, diagnostic unit 16 may diagnose that thelevel of the resilience of the software is lower than the predeterminedlevel and that vehicle 50 is being hacked.

Accordingly, it is possible to diagnose the presence of hacking throughthe presence of a backdoor in the software. With this, it is possible toreduce damage due to the hacking of vehicle 50.

Furthermore, diagnostic unit 16 may obtain an operation log of vehicle50 via communication unit 11, and perform the diagnosis based on theoperation log.

Accordingly, it is possible to perform sufficient diagnosis using theoperation log. With this, damage due to the hacking of vehicle 50 can bereduced.

Furthermore, diagnostic unit 16 may determine that vehicle 50 is beinghacked when diagnostic unit 16 confirms, based on the operation log,that vehicle 50 is not following a predetermined operational regulation.

In this manner, sufficient diagnosis can be performed by confirming thatan operational regulation is not being followed.

With this, it is possible to reduce damage due to the hacking of vehicle50.

Furthermore, diagnostic unit 16 may perform the diagnosis with at leastone of a diagnosis time or a diagnosis amount which is differentdepending on whether vehicle 50 is parked, stopped, or traveling.

Accordingly, it is possible to perform an appropriate diagnosis that issuited to the state in which vehicle 50 is in, such as parked, stopped,traveling, etc. With this, damage due to the hacking of vehicle 50 canbe reduced.

Furthermore, when vehicle 50 is determined to be parked, diagnostic unit16 may perform the diagnosis with the at least one of the diagnosis timeor the diagnosis amount set to a greater value than when vehicle 50 istraveling or stopped.

Accordingly, it is possible to perform an appropriate diagnosis onvehicle 50 which is stopped. With this, it is possible to reduce damagedue to the hacking of vehicle 50.

Furthermore, when vehicle 50 is determined to be stopped, diagnosticunit 16 may perform the diagnosis with the at least one of the diagnosistime or the diagnosis amount set to value which is greater than a valueset when vehicle 50 is traveling and less than a value set when vehicle50 is parked.

Accordingly, it is possible to perform an appropriate diagnosis onvehicle 50 which is stopped. With this, it is possible to reduce damagedue to the hacking of vehicle 50.

Furthermore, when vehicle 50 is determined to be traveling, diagnosticunit 16 may perform the diagnosis with the at least one of the diagnosistime or the diagnosis amount set to a lesser value than when vehicle 50is stopped or parked.

Accordingly, even when vehicle 50 is traveling, a matching appropriatediagnosis can be performed. With this, it is possible to reduce damagedue to the hacking of vehicle 50.

Lighting system 1D according to the present embodiment includes thelighting device described above and information terminal 70 thatcommunicates with the lighting device.

Accordingly, information as to whether vehicle 50 is being hacked can besent to information terminal 70. With this, a user which obtains theinformation can immediately take measures to cope with vehicle 50 thathas been hacked. With this, it is possible to reduce damage due to thehacking of vehicle 50.

Furthermore, diagnostic unit 16 may start the diagnosis when, aftervehicle 50 is parked in a parking space, information terminal 70 isseparated from parking space 91 by more than a predetermined distance.

With vehicle diagnostic system 1D, the presence of hacking of vehicle 50can be diagnosed at an opportunity where vehicle 50 is parked in parkingspace 91. In this way, damage due to the hacking of vehicle 50 can bereduced.

Furthermore, diagnostic unit 16 of the lighting device may end thediagnosis when, after the diagnosis of vehicle 50 which is parked inparking space 91 is started, information terminal 70 comes to within apredetermined distance of parking space 91.

With vehicle diagnostic system 1D, the presence of hacking of vehicle 50can be diagnosed at an opportunity where vehicle 50 is parked in parkingspace 91. In this way, damage due to the hacking of vehicle 50 can bereduced.

Lighting system 1E according to the foregoing embodiments includes:lighting device 10E including communication unit 11 that communicateswith vehicle 50 which drives autonomously, and light emitter 12 thatemits illumination light onto at least one of vehicle 50, road 92 onwhich vehicle 50 travels, or parking space 91 in which vehicle 50 parks;and vehicle diagnostic device 30E that is communicatively connected tocommunication unit 11 and performs, via communication unit 11, diagnosisas to whether vehicle 50 is being hacked.

Accordingly, even when vehicle 50 is traveling on road 92 or is parkedin parking space 91, it is possible to perform diagnosis as to whethervehicle 50 is being hacked. With this, it is possible to reduce damagedue to the hacking of vehicle 50.

Lighting system 1C according to the foregoing embodiments includes:lighting device 10C that emits illumination light onto at least one ofvehicle 50 which drives autonomously, road 92 on which vehicle 50travels, or parking space 91 in which vehicle 50 parks; and vehiclediagnostic device 30C including communication unit 31 that communicateswith lighting device 10C and vehicle 50, and diagnostic unit 36 thatperforms, via communication unit 31, diagnosis as to whether vehicle 50is being hacked.

Lighting system 1C can also appropriately perform diagnosis as towhether vehicle 50 is being hacked. With this, it is possible to reducedamage due to the hacking of vehicle 50.

Lighting device 10F according to the foregoing embodiments includes:communication unit 11 that communicates with mobile body 81 which drivesautonomously; diagnostic unit 16 that performs, via communication unit11, diagnosis as to whether mobile body 80 is being hacked; and lightemitter 12 that emits illumination light onto at least one of mobilebody 80, road 92 along travel path 97 in which mobile body 80 travels,or waiting area 96 in which mobile body 80 waits.

Since lighting device 10F can perform diagnosis as to whether mobilebody 80 is being hacked, it is possible to reduce damage due to thehacking of mobile body 80.

Furthermore, mobile body 80 may be an unmanned aircraft.

Accordingly, since it is possible to diagnose whether the unmannedaircraft is being hacked, it is possible to reduce damage due to thehacking of the unmanned aircraft.

Furthermore, diagnostic unit 16 may perform the diagnosis on mobile body80 which is waiting in waiting area 96, when the lighting state of lightemitter 12 changes. Moreover, diagnostic unit 16 may perform thediagnosis when light emitter 12 changes from an on state to an off stateor a dimmed state or changes lighting color. Furthermore, diagnosticunit 16 may end the diagnosis when the lighting state of light emitter12 changes again after changing from the on state to the off state orthe dimmed state, or after changing the lighting color.

Furthermore, communication unit 11 may start communication with mobilebody 80, with visible light communication from light emitter 12 tomobile body 80 as a trigger.

Furthermore, when diagnostic unit 16 diagnoses that mobile body 80 isbeing hacked, light emitter 12 may notify that mobile body 80 is beinghacked, by using the illumination light of light emitter 12. Inaddition, light emitter 12 may perform the notification by projectingthe illumination light onto at least one of mobile body 80 or waitingarea 96.

Furthermore, diagnostic unit 16 may perform the diagnosis based on ananswer to a question asked to mobile body 80. Moreover, diagnostic unit16 may perform the diagnosis by checking resilience of software whichruns a travel system provided in mobile body 80, via communication unit11. Furthermore, diagnostic unit 16 may obtain an operation log ofmobile body 80 via communication unit 11, and perform the diagnosisbased on the operation log.

Furthermore, lighting system 1G according to the foregoing embodimentincludes: lighting device 10G which includes communication unit 11 thatcommunicates with mobile body 80 which drives autonomously, and lightemitter 12 that emits illumination light onto at least one of mobilebody 80, road 92 along travel path 97 in which mobile body 80 travels,or waiting area 96 at which mobile body 80 waits; and mobile bodydiagnostic device 30G that is communicatively connected to communicationunit 11 and performs, via communication unit 11, diagnosis as to whethermobile body 80 is being hacked.

Accordingly, even when mobile body 80 is traveling along travel path 97,or waiting at waiting area 96, it is possible to perform diagnosis as towhether mobile body 80 is being hacked. With this, it is possible toreduce damage due to the hacking of mobile body 80.

OTHER EMBODIMENTS

Although Embodiments 1 to 8 of the present disclosure have beendescribed above, the present disclosure is not limited to lightingdevices 10 to 10G and lighting systems 1 to 1G described above.

Although diagnostic unit 16 or 36 diagnoses vehicle 50 or the like whenthe lighting state of light emitter 12 changes in Embodiments 1 to 8,the present disclosure is not limited to this. For example, diagnosticunit 16 or 36 may perform diagnosis when detector 13 detects vehicle 50or the like, even if the lighting state of light emitter 12 has notchanged.

When performing diagnosis of vehicle 50 or the like by asking a questionthat is uniquely answered shown in FIG. 3 , diagnostic unit 16 or 36according to Embodiments 1 to 8 may diagnose that vehicle 50 or the likeis being hacked when the answer to the question contains a wrong answer,a misspelling, a wrong language, or the like.

Although lighting devices including diagnostic unit 16 that diagnoseswhether vehicle 50 or the like is being hacked have been described inthe above embodiments, the embodiments described above can be applied toother diagnoses of vehicle 50 or the like.

For example, the lighting device may include communication unit 11 thatcommunicates with vehicle 50 that is autonomously driving, diagnosticunit 16 that diagnoses, via communication unit 11, whether vehicle 50has been zombified, and light emitter 12 that can emit illuminationlight to at least one of vehicle 50, road 92 on which vehicle 50travels, or parking space 91 in which vehicle 50 is parked. That“vehicle 50 is zombified” means at least one of a state of vehicle 50being hacked or a state of vehicle 50 being infected with a computervirus. Whether vehicle 50 is infected with a computer virus can bediagnosed by detecting whether a computer program that makes vehicle 50travel is normally operating.

The operations of the lighting devices according to Embodiments 1 to 8described above may be implemented by a program stored in memory 15 a.That is, a program including a step of changing the lighting state oflight emitter 12 that emits illumination light to vehicle 50, and a stepof communicating with vehicle 50 using communication unit 11 to diagnosewhether vehicle 50 is being hacked after the step described above may bestored in memory 15 a, and the operations of lighting devices 10 to 10Gmay be implemented by the program stored in memory 15 a.

Furthermore, each of the controllers according to above-describedEmbodiments 1 to 8 is implemented typically as a large-scale integration(LSI), which is an integrated circuit (IC). They may take the form ofindividual chips, or some or all of them may be encapsulated into asingle chip.

Moreover, the integrated circuit is not limited to an LSI, and may beimplemented as a dedicated circuit or a general-purpose processor.Alternatively, a field programmable gate array (FPGA) that allows forprogramming after the manufacture of an LSI, or a reconfigurableprocessor that allows for reconfiguration of the connection and thesetting of circuit cells inside an LSI may be employed.

It should be noted that, in foregoing Embodiments 1 to 8, the respectivestructural components may be implemented as dedicated hardware or may berealized by executing a software program suited to such structuralcomponents. Alternatively, the respective structural components may beimplemented by a program executor such as a CPU or a processor readingout and executing the software program recorded in a recording mediumsuch as a hard disk or a semiconductor memory.

Furthermore, the numerical figures used above are all given as examplesto specifically describe the present disclosure, and thus theembodiments of the present disclosure are not limited by the numericalfigures that have been given as examples.

Also, the divisions of the functional blocks shown in the block diagramsare mere examples, and thus a plurality of functional blocks may beimplemented as a single functional block, or a single functional blockmay be divided into a plurality of functional blocks, or one or morefunctions may be moved to another functional block. Moreover, thefunctions of a plurality of functional blocks having similar functionsmay be processed by single hardware or software in a parallelized ortime-divided manner.

Furthermore, the processing order of executing the respective stepsshown in the flowcharts is a mere illustration for specificallydescribing the present disclosure, and thus may be an order other thanthe shown order. Moreover, one or more of the steps may be executedsimultaneously (in parallel) with another step.

The present disclosure includes forms obtained by making variousmodifications to Embodiments 1 to 8 which can be conceived by thoseskilled in the art, as well as forms realized by arbitrarily combiningstructural components and functions in Embodiments 1 to 8 withoutdeparting from the essence of the present disclosure.

REFERENCE SIGNS LIST

-   -   1, 1A, 1B, 1C, 1D, 1E, 1F, 1G lighting system    -   10, 10A, 10C, 10D, 10E, 10F, 10G lighting device    -   11 communication unit    -   12 light emitter    -   13 detector    -   16 diagnostic unit    -   30B, 30C, 30E vehicle diagnostic device    -   30G mobile body diagnostic device    -   50 vehicle    -   70 information terminal    -   80 mobile body    -   91 parking space    -   92 road    -   96 waiting area    -   97 travel path

1. A lighting device comprising: a communication unit that communicateswith a vehicle which drives autonomously; a diagnostic unit thatperforms, via the communication unit, diagnosis as to whether thevehicle is being hacked; and a light emitter that emits illuminationlight onto at least one of the vehicle, a road on which the vehicletravels, or a parking space in which the vehicle parks.
 2. The lightingdevice according to claim 1, wherein the diagnostic unit performs thediagnosis on the vehicle which is parked in the parking space, when alighting state of the light emitter changes.
 3. The lighting deviceaccording to claim 2, wherein the diagnostic unit performs the diagnosiswhen the light emitter changes from an on state to an off state or adimmed state or changes lighting color.
 4. The lighting device accordingto claim 3, wherein the diagnostic unit ends the diagnosis when thelighting state of the light emitter changes again after changing fromthe on state to the off state or the dimmed state, or after changing thelighting color.
 5. The lighting device according to claim 1, wherein thecommunication unit starts communication with the vehicle, with visiblelight communication from the light emitter to the vehicle as a trigger.6. The lighting device according to claim 1, wherein when the diagnosticunit diagnoses that the vehicle is being hacked, the light emitternotifies that the vehicle is being hacked, by using an illuminationlight of the light emitter.
 7. The lighting device according to claim 6,wherein the light emitter performs the notification by projecting theillumination light onto at least one of the vehicle or the parkingspace.
 8. The lighting device according to claim 1, wherein when thediagnostic unit diagnoses that the vehicle is being hacked, the lightingdevice notifies a computer communicatively connected to the lightingdevice that the vehicle is being hacked.
 9. The lighting deviceaccording to claim 1, wherein when the diagnostic unit diagnoses thatthe vehicle is being hacked, the lighting device notifies that thevehicle is being hacked, by sending an electronic mail to apre-registered mail address.
 10. The lighting device according to claim1, wherein the diagnostic unit performs the diagnosis based on an answerto a question to the vehicle.
 11. The lighting device according to claim10, wherein the diagnostic unit performs the diagnosis based on at leastone of an answering time or an answering tendency to a plurality ofquestions.
 12. The lighting device according to claim 11, wherein thediagnostic unit asks the vehicle a question having a uniquely-determinedanswer via the communication unit, and diagnoses that the vehicle isbeing hacked when the answering time to the question is slower than apredetermined time.
 13. The lighting device according to claim 11,wherein the diagnostic unit asks the vehicle questions having answersthat are non-uniquely-determined via the communication unit, anddiagnoses that the vehicle is being hacked when an amount of variationin the answers to the questions is smaller than a predetermined amountof variation.
 14. The lighting device according to claim 1, wherein thediagnostic unit performs the diagnosis by checking resilience ofsoftware which runs a travel system provided in the vehicle, via thecommunication unit.
 15. The lighting device according to claim 14,wherein the diagnostic unit diagnoses that the vehicle is being hackedwhen a level of the resilience of the software is lower than apredetermined level.
 16. The lighting device according to claim 14,wherein the diagnostic unit checks the resilience of the software byperforming at least one of a denial-of-service (DoS) attack or a bufferoverflow attack on the software.
 17. The lighting device according toclaim 16, wherein when the DoS attack causes the level of the resilienceof the software to become lower than the predetermined level, thediagnostic unit continues the DoS attack until the software ceases tofunction.
 18. The lighting device according to claim 14, wherein thediagnostic unit checks the resilience of the software by performingtransmission of trap data to the software.
 19. The lighting deviceaccording to claim 18, wherein when a backdoor to the software is foundthrough the transmission of the trap data, the diagnostic unit diagnosesthat the level of the resilience of the software is lower than thepredetermined level and that the vehicle is being hacked.
 20. Thelighting device according to claim 1, wherein the diagnostic unitobtains an operation log of the vehicle via the communication unit, andperforms the diagnosis based on the operation log.
 21. The lightingdevice according to claim 20, wherein the diagnostic unit determinesthat the vehicle is being hacked when the diagnostic unit confirms,based on the operation log, that the vehicle is not following apredetermined operational regulation.
 22. The lighting device accordingto claim 1, wherein the diagnostic unit performs the diagnosis with atleast one of a diagnosis time or a diagnosis amount which is differentdepending on whether the vehicle is parked, stopped, or traveling. 23.The lighting device according to claim 22, wherein when the vehicle isdetermined to be parked, the diagnostic unit performs the diagnosis withthe at least one of the diagnosis time or the diagnosis amount set to agreater value than when the vehicle is traveling or stopped.
 24. Thelighting device according to claim 22, wherein when the vehicle isdetermined to be stopped, the diagnostic unit performs the diagnosiswith the at least one of the diagnosis time or the diagnosis amount setto value which is greater than a value set when the vehicle is travelingand less than a value set when the vehicle is parked.
 25. The lightingdevice according to claim 22, wherein when the vehicle is determined tobe traveling, the diagnostic unit performs the diagnosis with the atleast one of the diagnosis time or the diagnosis amount set to a lesservalue than when the vehicle is stopped or parked.
 26. A lighting systemcomprising: the lighting device according to claim 1; and an informationterminal that communicates with the lighting device.
 27. The lightingsystem according to claim 26, wherein the diagnostic unit starts thediagnosis when, after the vehicle is parked in a parking space, theinformation terminal is separated from the parking space by more than apredetermined distance.
 28. The lighting system according to claim 26,wherein the diagnostic unit of the lighting device ends the diagnosiswhen, after the diagnosis of the vehicle which is parked in the parkingspace is started, the information terminal comes to within apredetermined distance of the parking space.
 29. A lighting systemcomprising: a lighting device including: a communication unit thatcommunicates with a vehicle which drives autonomously; and a lightemitter that emits illumination light onto at least one of the vehicle,a road on which the vehicle travels, or a parking space in which thevehicle parks; and a vehicle diagnostic device that is communicativelyconnected to the communication unit and performs, via the communicationunit, diagnosis as to whether the vehicle is being hacked.
 30. Alighting system comprising: a lighting device that emits illuminationlight onto at least one of a vehicle which drives autonomously, a roadon which the vehicle travels, or a parking space in which the vehicleparks; and a vehicle diagnostic device including: a communication unitthat communicates with the lighting device and the vehicle; and adiagnostic unit that performs, via the communication unit, diagnosis asto whether the vehicle is being hacked.
 31. A lighting devicecomprising: a communication unit that communicates with a mobile bodywhich drives autonomously; a diagnostic unit that performs, via thecommunication unit, diagnosis as to whether the mobile body is beinghacked; and a light emitter that emits illumination light onto at leastone of the mobile body, a road along a travel path in which the mobilebody travels, or a waiting area in which the mobile body waits.
 32. Thelighting device according to claim 31, wherein the mobile body is anunmanned aircraft.